Connect MCP · SNAP Docs

Connect MCP / BEFORE YOU CONNECT

Approve once in the browser, then the agent calls on its own

No API key is copied anywhere. You approve once in the browser, and from then on the client holds and renews the token.

What you getSeven read-only FX reference tools: spot, forward, swap point, the full term structure, the tenor list, a text chart, and a market briefing. None of them place orders or move funds.

What you needA developer console session and an active MCP subscription entitlement. In the web MCP Lab, choose Connect MCP and approve SNAP MCP Lab access. Website sign-in alone is not an MCP token. Reloading the page requires reconnecting because tokens are kept only in memory.

Check these before approvingThe client name and the address it returns to, the Account, and the two permissions: kfi.mcp/connect and kfi.mcp/rates.read. Approval is all or nothing. If anything looks wrong, close the window; nothing has been issued.

MCP server URL

https://snap-api.kustodyfi.com/mcp

Connect MCP / CLAUDE CODE

Connect from the Claude Code CLI

Two commands: register the address, then authenticate. The browser opens for the approval and returns to Claude Code on its own.

Open connection management

Register the server

This only records the address. Nothing is authenticated yet.

Command

claude mcp add --transport http kustodyfi-snap https://snap-api.kustodyfi.com/mcp

Confirm it connected

A session that started before you authenticated will not see the tools. Open a new session and they appear.

Command

claude mcp list

Expected output

kustodyfi-snap: https://snap-api.kustodyfi.com/mcp (HTTP) - ✔ Connected

Connect MCP / CLAUDE DESKTOP

Connect from Claude Desktop

Claude Desktop adds the server through its settings rather than a command, then shows the same approval screen as the terminal clients.

Open connection management

Add a custom connector

In Settings, open Connectors, add a custom connector, and paste the server URL. There is no client ID or secret to supply.

MCP server URL

https://snap-api.kustodyfi.com/mcp

Approve in the browser

The approval screen is the one described in Before you connect. Check the client name, the Account, and the two permissions.

Confirm it connected

The connector shows as connected in settings, and the tools become available in a new conversation.

Connect MCP / CODEX

Connect from Codex

Codex keeps registering the server separate from authenticating with it, so it takes two commands as well.

Open connection management

Register the server

The url flag selects the streamable HTTP transport. Without it Codex expects a command to launch instead.

Command

codex mcp add kustodyfi-snap --url https://snap-api.kustodyfi.com/mcp

Confirm it connected

codex mcp get prints the stored server, and the tools become available in a new task.

Command

codex mcp get kustodyfi-snap

Connect MCP / MANAGE THE CONNECTION

See what is connected, and take it back

Approvals live on the server, not in the client. Removing the server locally leaves the approval standing.

Open connection management

See what is connected: MCP connection management in SNAP lists every approved client together with the Account it is bound to.
Disconnect: Disconnecting in SNAP kills the token and the next tool call gets 401. Removing the server in the client only clears your local registration and leaves the approval in place.
When you have to approve again: Usually never. Access tokens last 30 minutes and the client renews them; the renewal right lasts 90 days. You approve again only after disconnecting, after 90 days unused, or after an operational revocation.
When it does not work: Stuck on account selection means the session has not chosen an Account and there is no picker yet, so sign in again as the Account you want. A repeating sign-in screen means the session is not a developer console session. Connected but no tools means the session predates the approval, so open a new one.