Skip to main content
Any MCP-capable client can connect to your project’s endpoint — remote SSE (FastMCP) at <pod-address>/mcp/sse, authenticated with an X-Api-Token header. Get the URL and a paired token with:
See connect and mcp for the full flag reference.

Claude Code

Cursor

~/.cursor/mcp.json (or your project’s .cursor/mcp.json):

Codex

Codex speaks stdio only, not remote SSE with custom headers, so it goes through the mcp-remote bridge. ~/.codex/config.toml:

Claude Desktop

Same bridge situation as Codex — Claude Desktop’s config is stdio-only and can’t send custom headers natively. claude_desktop_config.json:

Any other MCP client

If your client isn’t listed above, the raw connection facts:

SportsClaw

SportsClaw is the reference external agent this connection flow was built around — see Ecosystem → SportsClaw for its own sportsclaw mcp add command and how it fits together end to end.
  • MCP Overview — the shared endpoint these snippets connect to.
  • connect — mint a durable, project-scoped token instead of using an ambient session/API key.