Grok CrossFin transfer

How to: Grok CrossFin transfer

client:Grok transport:streamable-http tool:transfer

Add CrossFin to Grok

01
Open .mcp.json (in your project root) and merge this in. Keep any servers already there.

{
  "mcpServers": {
    "crossfin": {
      "type": "http",
      "url": "https://crossfin.dev/api/mcp"
    }
  }
}

02
Save the file and restart Grok.
03
Ask for something transfer does. Grok lists the server's tools on connect and calls transfer itself — you do not invoke it by name.
04
If nothing happens, check the server is running and that CrossFin's identifier in your config matches the one above exactly.

Grok Build reads Claude Code's .mcp.json and Claude Desktop's config unchanged, so a server you have already set up there needs nothing new. The Grok web app and X integration do not take custom servers. Grok docs

Set these first

CrossFin will not start until these are set, so transfer never becomes available.

EVM_PRIVATE_KEY
CROSSFIN_API_URL
CROSSFIN_LEDGER_PATH

Same tool, other clients

This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what the server actually exposes, not what its listing claims.

Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.

CrossFin MCP server