Skip to main content
Atako runs a Model Context Protocol (MCP) server at https://api.atako.ai/mcp, so an AI client you already use — Claude Code, Claude Desktop, Cursor, ChatGPT developer mode, or any other MCP client — can read and act on your Atako account directly: your agents, their chat history and files, integration connections, activity, credits, and subscription.
Most tools read existing state. Some now write too: create, rename, end, and resume agents; send a message and wait for the reply; upload a file to an agent; connect an integration and grant it to an agent. Two things still need you in a browser — an OAuth integration connection needs your consent on the provider’s own page, and any billing/subscription change happens on app.atako.ai — no tool can do either for you.
Jump to the quickstart for copy-pasteable client configs.

​
Connecting

You need a programmatic API key (aik_…) from Settings → API keys. Point your MCP client at the URL below with that key as a Bearer token:
Transport is Streamable HTTP (the current MCP spec’s recommended transport) — no separate install for most clients, since they speak it natively. A key acts as its owning user: an MCP client connected with your key can do exactly what you’d be able to do logged into the app — read and manage your own agents, plus any agent your teammates created that you have access to through a shared team or company-wide visibility. A read key only gets the read-only tools; billing changes stay in the app for every key (see API keys).

​
Toolsets

88 tools is a lot for some clients. Load only what you need with ?toolsets=:
Without ?toolsets=, every tool is served.

​
Try it

Some things you can ask, once connected:
  • “List my Atako agents and tell me which ones are idle.”
  • “Create an agent that triages my Zendesk tickets and drafts replies.”
  • “Send my support agent a message asking for today’s ticket count, and wait for its reply.”
  • “Connect my GitHub token and grant it to my engineering agent, read-only.”
  • “What’s my credit balance and how many agent seats do I have left?”
  • “On the Launch project, move every card assigned to Ada to Done and summarize the wiki page ‘Brief’.”
  • “Which questions are my agents waiting on me for? Answer the tone one with ‘Formal’.”

​
Tools

​
Read

​
Write

​
Projects (toolset projects)

Kanban, card comments and wiki of your company’s projects — the same rules as the app (a project outside your company is “not found”; archiving needs an admin or the creator). A project’s space is a free-form label that groups projects (one per project, 60 characters max); reuse the exact spelling of an existing space.

​
Organization, dashboard, webhooks, email, notifications

Toolsets organization, dashboard, webhooks, email and notifications. Each tool runs the matching REST route, with its rules: company-wide views (dashboard, members) need a company admin. A public, unauthenticated endpoint at https://api.atako.ai/mcp/public also exposes 3 marketing tools with no API key required — get_pricing, list_use_cases, and list_integration_pages — useful for an assistant researching Atako itself rather than acting on your account.

​
Scheduling and delegation are agent-authored

There’s no create_cron_job or create_sub_agent tool, on purpose: an agent schedules its own recurring tasks and spawns its own sub-agents while it works, in response to being asked in a normal conversation — not through a separate creation API. Tell the agent what you want (“every Monday at 9am, check X and send me a summary”) and then use list_cron_jobs to confirm what it set up and inspect its run history.

​
Two things still need a browser

  • OAuth integrations — get_connect_url gets you the authorization URL, but finishing an OAuth consent screen needs you in an actual browser. For a provider that just needs a pasted API key/token instead, create_integration_connection works with no browser step at all.
  • Billing and subscription changes — there’s no MCP tool for this at all. Go to app.atako.ai → Settings → Billing.

​
Resources & prompts

  • Resources: atako://agents/{id} (same shape as get_agent), atako://agents/{id}/files (same shape as list_agent_files), and atako://docs/quickstart (this product’s own quickstart guide, for a client that wants to ground itself in what Atako is before calling any tool).
  • Prompts: diagnose_agent_issue (pulls an agent’s state, activity, and recent messages together to help figure out why it seems stuck), weekly_credits_report (a quick credits/subscription/agent-roster summary), create_support_agent_from_brief (turns a free-form description into a structured create_agent call), and connect_integration_wizard (walks through connecting one provider end-to-end, picking the right tool for how it authenticates).

​
Find Atako in MCP catalogues

Atako ships a machine-readable manifest for the official MCP registry (apps/api/server.json in aiybiz/aiybiz-next, namespace ai.atako/mcp) describing both endpoints above. Third-party catalogues (Smithery, Glama, PulseMCP, mcp.so, the Cursor directory) can index this server from that registry entry or from a direct submission — check each catalogue for Atako’s current listing status rather than assuming one exists yet.

​
What’s next

OAuth 2.1 with Dynamic Client Registration — a one-click “connect” experience from claude.ai/ChatGPT connectors instead of pasting an API key — is planned for a future release, along with a granular scope model narrower than “this key can do everything its owner can”.