Documentation MCP

Connect Cursor, Windsurf, Claude, and other AI tools to Tatum docs and APIs. Search guides, explore OpenAPI endpoints, and optionally run live API calls with your Tatum API key.

Connect your AI assistant to Tatum developer documentation and the Tatum REST API (via OpenAPI) in one place. The Documentation MCP server at https://docs.tatum.io/mcp lets agents search guides, look up endpoints and schemas, and—if you add a Tatum API key—execute real requests against Tatum.

No API key is required to browse docs and explore the API spec. Add your key only when you want the assistant to call Tatum on your behalf.

🤖
Looking for Tatum Blockchain MCP?
Tatum also offers an MCP server for the Blockchain Data API and RPC Gateway, so LLMs can read and write blockchain data across 130+ networks.
👉 Tatum Blockchain MCP

What is MCP?

Model Context Protocol (MCP) is an open standard for connecting AI apps to external tools and data. The Tatum Documentation MCP server exposes:

Capability	Without API key	With API key (`X-API-Key`)
Search and read guide pages	Yes	Yes
List, search, and inspect API endpoints	Yes	Yes
Execute live API requests (`execute-request`)	No	Yes

Headers you set in your MCP client config are forwarded to Tatum when the assistant uses execute-request, so your dashboard key authenticates those calls the same way as REST authentication.

Connect in under a minute

Add to ~/.cursor/mcp.json (or project .cursor/mcp.json):

Docs and API spec only:

{
  "mcpServers": {
    "tatumdocs": {
      "url": "https://docs.tatum.io/mcp"
    }
  }
}

Docs + live API calls — add your Tatum API key:

{
  "mcpServers": {
    "tatumdocs": {
      "url": "https://docs.tatum.io/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Restart Cursor (or reload MCP servers) after saving.

🔑
Keep your API key private. Do not commit mcp.json with real keys to git. Use environment-specific config or a secrets manager for shared machines.

Available tools

The server exposes OpenAPI tools (from Tatum’s published specs) and documentation tools (full-text search over guides).

OpenAPI tools

Use these to discover endpoints, read request/response shapes, and optionally call Tatum.

Tool	What it does
`list-specs`	Lists all OpenAPI specs in the project (use the `title` when a tool requires it).
`list-endpoints`	Returns API paths and HTTP methods with summaries for a spec.
`search-endpoints`	Case-insensitive search across paths, operations, and parameters.
`get-endpoint`	Full detail for one endpoint: parameters, body schema, security, servers.
`execute-request`	Runs a live HTTP request (HAR format). Requires `X-API-Key` in MCP headers for authenticated Tatum calls.

Typical flow: list-specs → search-endpoints or list-endpoints → get-endpoint → generate code or execute-request.

Documentation tools

Tool	What it does
`search`	Full-text search across guide pages; returns titles, IDs, and URLs.
`fetch`	Returns the full content of a guide page by ID (use `search` first to get the ID).

Typical flow: search → fetch → answer or generate code using accurate doc content.

Example prompts

Copy these into your assistant after MCP is connected.

Explore without an API key

Use the Tatum docs MCP tools to find how wallet balances work on Ethereum.
Summarize the relevant guide pages and list the REST endpoints I'd need.

Search the Tatum OpenAPI spec for "notification" and explain the webhook
subscription endpoints—parameters, auth, and example request bodies.

Build integration code (API key optional)

Using Tatum MCP, look up POST /v4/subscription and write a Node.js function
that creates a webhook subscription. Use the real schema from get-endpoint—
no guessed fields.

Live API calls (API key required in mcp.json)

Using execute-request and my configured API key, call the Tatum API to get
the native balance for this Ethereum address: 0x... Show the raw response
and confirm it matches the documented schema.

Verify your setup

Open your AI tool and start a new chat.
Confirm tatumdocs (or your server name) appears in the MCP / tools list.

Run a read-only check:

Use Tatum MCP search to find the authentication guide and summarize
how X-API-Key works.

If you added X-API-Key, test execution:

Use list-specs and search-endpoints to find a simple GET endpoint,
then execute-request against testnet with a minimal example.

If search works but execute-request returns 401, confirm the header name is X-API-Key, the key is valid in the dashboard, and you restarted the client after editing config.

MCP server URL

Environment	URL
Production (default)	`https://docs.tatum.io/mcp`

What is MCP?

Connect in under a minute

Available tools

OpenAPI tools

Documentation tools

Example prompts

Verify your setup

MCP server URL

Further reading