Atako MCP
Máy chủ MCP từ xa cho Atako, một nền tảng tác tử AI. 30 công cụ để liệt kê, tạo, nhắn tin và quản lý các tác tử Atako của bạn, tệp và tích hợp của chúng, cùng 3 công cụ công khai (giá cả, trường hợp sử dụng, tích hợp) không yêu cầu xác thực. HTTP có thể truyền phát, xác thực Bearer token (aik_...) cho điểm cuối đã xác thực. Điểm cuối đã xác thực: https://api.atako.ai/mcp - Điểm cuối công khai (không xác thực): https://api.atako.ai/mcp/public
Tài liệu
Atako MCP
Connect Claude Code, Claude Desktop, Cursor, or ChatGPT to your Atako account over the Model Context Protocol.
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.
[!NOTE]
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
Add the URL below to your MCP client. Claude, ChatGPT, Claude Code and Cursor discover Atako's OAuth sign-in on their own: you log in, choose read-only or read & write access, and approve. Any company member can connect; the client gets that member's own rights, never more. Connected apps are listed, and can be disconnected, in Settings → AI assistants.
URL: https://api.atako.ai/mcp
For scripts and CI, use a programmatic API key (aik_…)
from Settings → API keys instead, sent as a Bearer token:
Header: Authorization: Bearer aik_...
Transport is Streamable HTTP (the current MCP spec's recommended transport) — no separate install for most clients, since they speak it natively.
A connection acts as its owning user: an MCP client connected with your account or 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 connection or key only gets the read-only tools; billing changes stay in the app for every key (see API keys).
Toolsets
97 tools is a lot for some clients. Load only what you need with ?toolsets=:
https://api.atako.ai/mcp?toolsets=projects,agents,messages
| Toolset | Covers |
|---|---|
agents | Agents (create, profile, lifecycle), notices |
messages | Chat, conversations (sessions), cron jobs, sub-agents, activity |
files | Context files and agent file grants |
integrations | Integration catalog, connections, grants |
billing | Credits, subscription, models, harnesses |
projects | Projects, kanban, card comments, wiki |
organization | Teams, org chart, members, search, company knowledge |
dashboard | Company dashboard, credits usage, integration logs (admins) |
webhooks | Agents' inbound webhooks |
email | Agents' email addresses, threads, approvals |
notifications | Your notifications |
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
| Tool | What it returns |
|---|---|
list_agents | Every agent you can see, with status and a preview of the last message |
get_agent | Full detail for one agent |
whoami | Your identity, company, and subscription plan |
list_messages | Your chat history with one agent |
wait_for_reply | Blocks (up to 25s) for an agent's next reply — call right after send_message |
list_cron_jobs | An agent's recurring scheduled tasks and their run history |
list_sub_agents | Sub-agents an agent has spawned to delegate work |
list_interagent_messages | Messages an agent exchanged with company peers |
list_activity | An agent's live activity timeline (turns, tool calls, sub-agents) |
get_activity_state | Whether an agent is currently working |
list_agent_files | Files an agent can currently reach |
list_integration_catalog | Every third-party integration Atako supports |
list_integration_connections | Your own connected integrations |
list_agent_integration_grants | Which connections an agent may use, and how |
get_connect_url | Starts an OAuth connection, returns the URL to open in a browser |
get_credits | Your company's credit balance and consumption this period |
get_subscription | Your company's plan, status, and active-agent license usage |
list_models | Suggested, favorite and recent models; search covers the whole catalog (no prices) |
list_harnesses | Execution harnesses available when creating an agent |
list_conversations | Your conversations (sessions) with an agent |
list_notices | Questions agents raised to you, open ones first |
get_notice | One notice with its options and answer |
list_agent_file_grants | Which Context files and folders an agent can reach |
Write
| Tool | What it does |
|---|---|
create_agent | Creates a new agent — only name is required |
update_agent_name | Renames an agent |
end_agent | Ends an active agent, freeing its seat |
resume_agent | Resumes a paused agent |
cancel_agent_provisioning | Cancels an agent still provisioning |
retry_agent_provisioning | Retries a failed provisioning |
send_message | Sends a chat message to an agent, optionally in a given conversationId (fire-and-forget — pair with wait_for_reply) |
steer_agent_turn | Adds an instruction to the turn an agent is running in a conversation (delivered after its current step, without interrupting it) |
stop_agent_turn | Stops the turn an agent is running in a conversation (the partial reply is kept, marked interrupted) |
upload_file_to_agent | Uploads a file (≤10 MiB, base64) and grants it to an agent, in one call |
create_integration_connection | Connects an integration by pasting an API key/token |
grant_integration_to_agent | Grants an agent access to a connection, and which actions |
revoke_integration_grant | Revokes an agent's access to an integration |
update_agent | Changes an agent's role, mission, instructions, business context or team |
set_agent_llm_key | Switches an agent between Atako inference and one of your LLM keys |
create_conversation | Opens a new conversation (session) — pass its id as conversationId |
update_conversation | Renames or archives a conversation |
respond_to_notice | Answers an agent's question |
grant_files_to_agent | Gives an agent access to Context files or folders |
revoke_file_grant | Removes an agent's access to a file or folder |
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 belongs to at most one space (a company-wide grouping, 60-character name). Give it with spaceId (from list_project_spaces) or with space (a name: the existing space of that name is reused, case-insensitively, otherwise it is created) — never both.
| Tool | What it does |
|---|---|
list_projects | Your company's projects (each with its spaceId and space), archived ones excluded by default; filter with one of spaceId, space or withoutSpace |
get_project | One project with its columns, cards, participants and wiki summary |
create_project | Creates a project, optionally with a spaceId or space, participants and starter columns/wiki page |
update_project | Changes name, description, tone, status or space (spaceId or space; null removes it) — overwrites without history (destructive, confirm first) |
list_project_spaces | Your company's project spaces (id, name, position, project count), empty ones included |
create_project_space | Creates an empty space (unique name, case-insensitive) |
update_project_space | Renames a space and/or changes its position |
delete_project_space | Deletes a space; its projects are kept and become space-less (destructive, confirm first) |
archive_project | Archives a project (restorable) |
restore_project | Restores an archived project |
add_project_column | Adds a kanban column |
update_project_column | Renames a column or changes its kind |
list_project_members | People and agents taking part in a project |
add_project_member | Adds a person or an agent to a project |
create_card | Creates a card in a column |
update_card | Edits a card (assignee, priority, labels, checklist, due date, blocked…) — overwrites without history (destructive, confirm first) |
move_card | Moves a card to a column and position |
delete_card | Removes a card from the kanban |
list_card_comments | A card's discussion thread |
add_card_comment | Comments on a card |
list_wiki_pages | The wiki as a page tree |
get_wiki_page | One page with its content and recent revisions |
create_wiki_page | Creates a markdown page |
update_wiki_page | Edits a page (every change is a revision) |
list_wiki_revisions | A page's revision history |
restore_wiki_revision | Restores an earlier revision |
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.
| Tool | What it does |
|---|---|
list_teams | Your company's teams |
get_team | One team with its positions |
get_org_chart | The reporting tree of people and agents, and its gaps |
list_company_members | People of your company and their permissions (admins) |
search | Searches agents, projects, cards, wiki, teams, people, files, conversations |
search_knowledge | Full-text search inside the content of pages, cards, projects, files and company context |
get_knowledge_item | One knowledge item's full text and linked items |
get_knowledge_tree | Company knowledge grouped by meaning, level by level |
export_knowledge | Starts a ZIP export (markdown + manifest) of what you can read |
get_knowledge_export | An export's status, then a download URL |
get_dashboard_overview | The company dashboard, last 24 hours by default (admins) |
get_credits_usage | Credit balance and consumption over a window (admins) |
list_integration_logs | The integration call journal (admins) |
list_dashboard_notices | Notices raised vs answered, per person (admins) |
get_storage_usage | Size of the company Context (admins) |
list_agent_webhooks | An agent's inbound webhook endpoints |
create_agent_webhook | Creates a webhook endpoint (URL and token shown once) |
rotate_agent_webhook | Rotates a webhook's URL token and/or secret |
test_agent_webhook | Sends a test payload through an endpoint |
list_webhook_events | Events received by an endpoint |
requeue_webhook_event | Delivers a skipped or quarantined event again |
get_agent_email | An agent's email address and settings |
list_agent_email_threads | An agent's email threads |
get_agent_email_thread | One thread with its messages |
approve_outbound_email | Approves an email waiting for approval |
reject_outbound_email | Rejects an email waiting for approval |
list_notifications | Your in-app notifications |
mark_notifications_read | Marks one or all notifications read |
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_urlgets 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_connectionworks 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 asget_agent),atako://agents/{id}/files(same shape aslist_agent_files), andatako://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 structuredcreate_agentcall), andconnect_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
A granular scope model, narrower than "this connection can do everything its owner can", is planned for a future release.
This documentation is built and hosted on Mintlify, a developer documentation platform.