Atako

ai.atakoPublished by atako.aiOfficial publisherv0.2.1Updated Oct 24, 2026

Remote MCP server to run your Atako AI agents: chat, projects, files, integrations and channels.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowCommunication & CollaborationAI & ML

Overview

AI-generated overview

Remote MCP server for the Atako AI-agent platform, letting an assistant read and act on agents, chat, projects, files, integrations and organization data.

What you can do
  • Manage agents: create agents, edit profiles and lifecycle, and handle notices
  • Chat and automation: conversations, messages, cron jobs, sub-agents and activity
  • Projects: projects, kanban boards, card comments and wiki pages
  • Files and integrations: context files, agent file grants, integration catalog, connections and grants
  • Organization and account: teams, org chart, members, search, notifications, credits, subscription and models
  • Admin and channels: company dashboard, credit usage, integration logs, inbound webhooks and agents' email threads and approvals
When to use it
Useful when a team already runs AI agents on Atako and wants an assistant such as Claude Code, Claude Desktop, Cursor or ChatGPT developer mode to inspect and operate that account without switching tools. A public, unauthenticated endpoint also exposes pricing, use cases and integration pages for read-only lookups.
Requirements
Remote Streamable HTTP endpoint hosted by Atako; nothing to install. The main endpoint requires an Atako API key (aik_...) sent as an Authorization Bearer header, created by a company admin under Settings → API keys. The key's read or read-and-write scope limits which tools are served. Toolsets can be restricted with a toolsets query parameter. A public endpoint needs no authentication.
Before you install
The API key is shown only once and grants access to a company account; a read-and-write key acts with the permissions of its owner, so prefer a read-scoped key where possible. Write tools can create and change agents, projects, files, integrations and webhooks. OAuth integrations return a consent URL to open in a browser. Billing and subscription changes are not exposed by any tool.

Installation

In SourceWeft

  1. Open Atako in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/ai.atako%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "atako": {
      "type": "http",
      "url": "https://api.atako.ai/mcp"
    }
  }
}

README

Atako MCP server

Atako is a platform of AI agents for companies. Its remote MCP server lets an MCP client (Claude Code, Claude Desktop, Cursor, ChatGPT developer mode…) read and act on an Atako account: agents, chat, files, integrations, projects, organization, billing state.

Registry entry: ai.atako/mcp (JSON) — manifest in server.json. Full documentation: docs.atako.ai.

This repository holds the registry manifest and connection instructions only. The server is hosted by Atako; there is nothing to install or run.

Endpoints

Both use the Streamable HTTP transport.

URLAuthTools
https://api.atako.ai/mcpAuthorization: Bearer aik_... (Atako API key)86
https://api.atako.ai/mcp/publicnone3: get_pricing, list_use_cases, list_integration_pages

API key

app.atako.ai → Settings → API keys → Create key (company admins). The key is shown once.

ScopeOver MCP
ReadRead-only tools only; write tools are neither listed nor callable.
Read & writeAll tools, with the permissions of the key's owner.

Billing and subscription changes are not exposed by any tool. OAuth integrations return a consent URL to open in a browser.

Toolsets

Restrict the served tools with ?toolsets= (comma-separated). Without it, all toolsets are served.

https://api.atako.ai/mcp?toolsets=agents,messages,projects
ToolsetToolsCovers
agents14Agents (create, profile, lifecycle), notices
messages11Chat, conversations, cron jobs, sub-agents, activity
files5Context files, agent file grants
integrations7Integration catalog, connections, grants
billing4Credits, subscription, models, harnesses
projects22Projects, kanban, card comments, wiki
organization5Teams, org chart, members, search
dashboard5Company dashboard, credit usage, integration logs (admins)
webhooks6Agents' inbound webhooks
email5Agents' email addresses, threads, approvals
notifications2Your notifications

Tool list: docs.atako.ai/developers/mcp/overview.

Client configuration

Claude Code

bash
claude mcp add --transport http atako https://api.atako.ai/mcp \  --header "Authorization: Bearer aik_..."

Claude Desktop, Cursor

Claude Desktop: Settings → Developer → Edit Config. Cursor: ~/.cursor/mcp.json or .cursor/mcp.json.

json
{  "mcpServers": {    "atako": {      "url": "https://api.atako.ai/mcp",      "headers": {        "Authorization": "Bearer aik_..."      }    }  }}

Public endpoint: same config with https://api.atako.ai/mcp/public and no headers.

License

MIT for the files in this repository. The Atako service is proprietary.

Source: README.md at commit 1214fff

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

2
  1. v0.2.1LatestSep 28, 2026
  2. v0.1.0Sep 16, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts