Skip to docs content
Browse documentation
On this page

Connect your agent

Minion is an MCP server. You use it from Claude, ChatGPT, Cursor, Codex, Claude Code, or any other AI agent that supports MCP — not from a separate Minion chat app.

The three-step Get started flow lives in Connect your agent and on /app/onboarding. This page is the per-app install reference.

Add the MCP server

  1. Open Get started (/app/onboarding). It shows your MCP URL with a copy button. On app.minion.codes the MCP URL is https://app.minion.codes/mcp; a preview or self-hosted deployment uses that origin's /mcp.
  2. Follow the steps for your app below.
  3. Sign in to Minion if asked, then approve access. Approving lets that agent act as you in this team.

After that, Connections (/app/connections) lists every app that has authorized, with a revoke button. It also holds the optional notes Minion adds to the instructions every one of your agents sees.

Client notes

  • Claude (claude.ai and Claude Desktop) — Settings, Connectors, Add custom connector. Paste the MCP URL, then sign in and approve. Remote servers are not configured through claude_desktop_config.json. After connecting, start a new chat and ask Claude to list Minion tools before the first task — Claude Desktop often does not bind MCP tools until that next turn.
  • ChatGPT — Settings, Apps and Connectors, turn on Developer mode, then Create. Paste the MCP URL, choose OAuth, then sign in and approve. Developer mode needs an eligible paid ChatGPT plan; in a managed workspace an admin may have to enable it.
  • Claude Code, Cursor, Codex and other headless clients — create an API key at /app/api-keys. The page shows the new key once, with a ready-made snippet for each client:
    • Claude Code: claude mcp add --transport http minion <url> --header "Authorization: Bearer <key>"
    • Cursor: an mcpServers.minion entry with url and headers.Authorization in .cursor/mcp.json.
    • Codex: a [mcp_servers.minion] table with url and http_headers in ~/.codex/config.toml.

API keys act as you. Every key expires (you pick up to 90 days), a key unused for 14 days stops working, and a member can hold up to 50 active keys and tokens. Owners and admins can see and revoke every member's keys.

Any other app that supports remote MCP over Streamable HTTP can use the same URL, either through OAuth or with a bearer API key in the Authorization header.

Coding vs non-coding agents

Using packages that already exist works well from chat apps. Creating or editing packages is smoother from a coding agent because those hosts edit files and iterate on code. Either kind can be first; see Connect your agent .

Where to go next