Connect other clients

Last updated 2026-08-16

Any client that speaks MCP over HTTP can connect to FM Fathom. The Connect to AI page in the portal shows every snippet on this page with your real URLs filled in, so the fastest path is usually to copy from there.

Claude Code

One command, then sign in:

claude mcp add --transport http fm-fathom-your-client https://fathom.fmfathom.com/mcp/c/your-client

Run /mcp inside Claude Code to complete the sign-in. Add --scope user if you want the connection available in every project, not just the current one.

Static access keys, for everything else

Some clients don't do the sign-in flow. For those, FM Fathom issues static access keys:

  1. On Connect to AI, under the client, choose Generate access key.
  2. Copy it immediately. For your security it's shown in full only once, at creation.
  3. Configure your client with the MCP URL https://fathom.fmfathom.com/mcp and an x-api-key header carrying the key. (An Authorization: Bearer header works too.) The key itself identifies the client, so this URL has no client slug in it.

Keys are checked on every request, so revoking one on the Connect to AI page cuts access immediately. Generate one key per tool if you like tidy revocation.

Codex

In Codex, add a custom MCP server with transport Streamable HTTP, the URL above, header name x-api-key, and the key as the header value. Leave the bearer-token field empty. The Connect to AI page also shows the equivalent config.toml block ready to paste.

Claude Code with a key

If you'd rather not use sign-in there:

claude mcp add --transport http fm-fathom-your-client https://fathom.fmfathom.com/mcp --header "x-api-key: YOUR_ACCESS_KEY"

Anything else

Point the client at https://fathom.fmfathom.com/mcp with the x-api-key header. If your client only takes a URL and can't send headers, check its docs for an "HTTP headers" or "custom headers" option; most current MCP clients have one.

Related