MCP server

Taka speaks MCP natively at https://api.taka.ai/mcp. Any MCP client, Claude Code, Claude Desktop, Cursor, and friends, gets the full surface over the same key and the same scopes as the REST API.

Connect a client

Claude Code: one command.

claude mcp add --transport http taka https://api.taka.ai/mcp \
  --header "Authorization: Bearer taka_live_..."

Everything else: paste the config block into your client's MCP settings.

{
  "mcpServers": {
    "taka": {
      "type": "http",
      "url": "https://api.taka.ai/mcp",
      "headers": { "Authorization": "Bearer taka_live_..." }
    }
  }
}

What the server exposes

• 41 tools covering posts, generation, scheduling, publishing, brand, and analytics.
• Four guided prompts: plan_my_week, review_and_approve, ship_this_post, and fix_my_brand_voice, each walking the agent through a full workflow.
• Live resources so the agent reads current state instead of guessing it: account, credits, brand, the upcoming calendar, and taka://service-contract, the honesty contract the server asks every agent to read first.

One boundary: media uploads are REST-only (POST /v1/public/media); everything else the tools cover.

Long work still comes back as jobs, and revision results still carry the honesty flags. Tools mirror the REST surface, so this reference doubles as the tool reference.

Keys and scopes

The MCP server enforces the key's scopes exactly like REST. Hand your agent a key without publish and it can draft all week without shipping anything.

The taka-agent skill

For Claude Code and Cursor, TakaAISocial/taka-agent packages full instructions in one install. For any other model, https://api.taka.ai/llms.txt is the whole surface in plain text.