Connect Agentda to your tools
Agentda has no task UI — your AI agent is the interface. That makes “integration” simpler than you might expect: your agent connects once via MCP, and task updates can flow into the chat rooms your team already uses.
How do I connect Claude (Desktop, Code, claude.ai)?
Enter your work email at myagentda.com, click the magic link, and add the MCP endpoint https://myagentda.com/api/mcp to your Claude (OAuth sign-in happens on first use). In Claude Code: claude mcp add --transport http agentda https://myagentda.com/api/mcp. Ready in about two minutes — this is the primary way to use Agentda.
Does Agentda work with MCP clients other than Claude?
Yes. Agentda is a standard remote MCP server (Streamable HTTP, OAuth 2.0 with PKCE and dynamic client registration). Any MCP-capable client — Cursor, other agent runtimes, custom agents — can connect to the same endpoint and use the same 17 tools.
How do I get task updates into Slack?
Create a Slack incoming webhook for your channel, then tell your agent: “Post task updates to our Slack channel” — it calls admin_tenant with set_webhook and the webhook URL (admins only). Agentda automatically sends Slack's { text } format. From then on, task events (created, delegated, accepted, completed …) appear as room messages.
How do I get task updates into Microsoft Teams?
Two ways. Room posts (recommended today): create a Power Automate flow with the “When a Teams webhook request is received” trigger, post the text field to your channel, and register the flow URL via set_webhook. Personal 1:1 chat messages via Microsoft Graph are built in as a channel and activate when an Entra ID app is configured (GRAPH_TENANT_ID / GRAPH_CLIENT_ID / GRAPH_CLIENT_SECRET); a richer Teams bot with action buttons is on the roadmap.
What about Zulip, Mattermost, Discord and other chat tools?
Any tool that accepts incoming webhooks works: register the webhook URL via set_webhook (https only, up to three per workspace). Agentda posts a compact JSON payload with a ready-to-display text field plus task number, title, and event text — Zulip and Mattermost consume it directly; for Discord use a small relay or bot that maps text to content.
How does Agentda fit agentic workspaces like Buzz or Kollab?
Directly — that's the native path. Agents in Buzz run on Claude Code, Codex, or Goose, and Kollab wires MCP servers behind its bots: in both cases the agent simply connects to the Agentda MCP endpoint itself and works with tasks, delegations, and history like any other agent. Room notifications via webhook work in addition, as soon as the platform exposes incoming webhooks.
What if my counterpart uses none of these tools?
Then email is enough. Delegate to any email address: the recipient gets a link to exactly that one task — no account, no app — and can accept, comment, and complete it. Replies to notification emails land as comments in the task history. Guests are always free.
How are webhook deliveries secured?
Webhooks are admins-only, https-only, and limited to three per workspace. Every delivery carries an X-Agentda-Signature header: an HMAC-SHA256 over “<timestamp>.<body>” with a per-webhook secret that is shown exactly once at setup. Verify it server-side to reject forged posts; a five-minute timestamp window guards against replays.
Last reviewed: 2026-07-26