MCP

MCP is the protocol agents (Claude Code, Claude Desktop, Cursor, Cline, OpenClaw and others) use to plug in external tools. Mixen runs its own MCP server over Streamable HTTP: the agent gets the models directly — ask a text model, generate an image, check the catalog and the balance — without writing a line of integration code.

Connecting

Authentication uses the same mxn-… key (Keys & authentication); the key’s scopes and rate limits carry over.

Claude Code:

claude mcp add --transport http mixen https://api.mixen.ai/v1/mcp \
  --header "Authorization: Bearer mxn-your-key"

Cursor (.cursor/mcp.json in the project root; add the file to .gitignore so the key never reaches the repository):

{
  "mcpServers": {
    "mixen": {
      "type": "http",
      "url": "https://api.mixen.ai/v1/mcp",
      "headers": {"Authorization": "Bearer mxn-your-key"}
    }
  }
}

Any other MCP client: URL https://api.mixen.ai/v1/mcp, Streamable HTTP transport, header Authorization: Bearer mxn-….

Tools

Tool	What it does
mixen_chat	Ask a text model: model, prompt, optionally system, reasoning_effort, max_tokens, web_search (auto/native/exa)
mixen_generate_image	Generate an image — the result arrives as an image the agent can see
mixen_list_models	Catalog: ids, types, prices in ₽
mixen_get_balance	Account balance
mixen_get_topup_link	Top-up payment link: amount (₽ 10–10000, or $ 1–200 with amount_usd=true), method — tochka/cryptobot/cryptocloud
mixen_list_transactions	Recent transactions: date, type, amount, model (limit 1–50, default 10)

Just tell the agent: “ask mixen what’s new” or “generate a cover via mixen” — it will call the tools on its own. When the balance runs out, the agent checks it with mixen_get_balance, hands you a payment link from mixen_get_topup_link, and reports spending via mixen_list_transactions.

Billing and limits

Usage is billed from the same balance as the bot, the cabinet and the API; charges show up in GET /v1/history (Tokens and billing). The key’s scopes apply (a chat-only key cannot generate images), and so does the shared limit — 60 requests per minute. Errors arrive as tool text: invalid api key, the top-up requirement, the rate-limit message.

Limitations

• No text streaming over MCP — a protocol limitation, not a backend one: by specification a tool result arrives as a single message and agents do not render partial text (only progress notifications are available). For streaming deltas use SSE /v1/chat/completions.
• Video, music, generation history and file storage are not exposed over MCP — they are available through the HTTP API.