TombaTomba
Start free
  • Documentation
  • API reference
  • SDKs & CLI
  • AI & MCP
  • Integrations
  • Enterprise
  • Migration guides

Find, verify and enrich B2B contacts from public sources, in the app, your spreadsheet or through the API.

GDPR & CCPA

// docs

  • API changelog
  • Support options
  • Security

// platform

  • Dashboard
  • Pricing
  • API status

// resources

  • Help center
  • Product updates
  • TombaBot crawler

// company

  • Website
  • Contact us
  • Edit or remove your data

© 2021–2026 Tomba.io

  • Terms of service
  • Privacy policy
  • Cookie policy
  • Security policy
  • GDPR
  • CCPA
Remote MCP server
Local MCP serverDocs for AI assistants
Agent payments (MPP)
AI & MCP

Local MCP server

@tomba-io/tomba-mcp-server is an MCP server that runs on your machine and calls the Tomba API with your key and secret. It provides the same 28 tools as the remote server. The remote MCP server needs no installation and also supports OAuth; Local server differences lists how the two servers behave differently.

Requirements

  • Node.js 18.20 or later. Earlier versions stop at startup with SyntaxError: Unexpected token 'with'.
  • A Tomba API key and secret. See Get your key and secret.

Run the server

Your MCP client usually starts the server for you, as shown in Configure a client. To check that the package installs and runs, print its version:

TerminalCode
npx -y @tomba-io/tomba-mcp-server --version

The server reads your credentials from two environment variables, and exits with Error: TOMBA_API_KEY and TOMBA_SECRET_KEY environment variables are required if either is missing:

VariableValue
TOMBA_API_KEYYour API key, ta_…
TOMBA_SECRET_KEYYour secret, ts_…

It accepts these options:

OptionDefaultDescription
--transport, -tstdiostdio to talk to the client that started it, or http to serve Streamable HTTP. See HTTP transport.
--port, -p3000Port for the HTTP transport
--version, -vPrint the version and exit
--help, -hPrint the options and exit

Configure a client

In each example, replace ta_xxxx and ts_xxxx with your key and secret. Keep configuration files that contain your secret out of version control.

Claude Desktop

In Claude Desktop, open Settings → Developer and select Edit Config. The file is at ~/Library/Application Support/Claude/claude_desktop_config.json on macOS and %APPDATA%\Claude\claude_desktop_config.json on Windows. Add the server, then quit and restart Claude Desktop:

Code
{ "mcpServers": { "tomba": { "command": "npx", "args": ["-y", "@tomba-io/tomba-mcp-server"], "env": { "TOMBA_API_KEY": "ta_xxxx", "TOMBA_SECRET_KEY": "ts_xxxx" } } } }

The same mcpServers entry works in the configuration files of Cursor, Windsurf, Gemini CLI, and Cline; Connect a client says where each client keeps its file.

Claude Code

TerminalCode
claude mcp add --scope user tomba \ -e TOMBA_API_KEY="$TOMBA_API_KEY" \ -e TOMBA_SECRET_KEY="$TOMBA_SECRET_KEY" \ -- npx -y @tomba-io/tomba-mcp-server

VS Code

Add the server to .vscode/mcp.json, or to the file that MCP: Open User Configuration opens. VS Code asks for the key and secret on first use and stores them securely:

Code
{ "inputs": [ { "type": "promptString", "id": "tomba-key", "description": "Tomba API key", "password": true }, { "type": "promptString", "id": "tomba-secret", "description": "Tomba secret", "password": true } ], "servers": { "tomba": { "type": "stdio", "command": "npx", "args": ["-y", "@tomba-io/tomba-mcp-server"], "env": { "TOMBA_API_KEY": "${input:tomba-key}", "TOMBA_SECRET_KEY": "${input:tomba-secret}" } } } }

Zed

Run zed: open settings file and add the server under context_servers:

Code
{ "context_servers": { "tomba": { "command": "npx", "args": ["-y", "@tomba-io/tomba-mcp-server"], "env": { "TOMBA_API_KEY": "ta_xxxx", "TOMBA_SECRET_KEY": "ts_xxxx" } } } }

Verify the connection

  1. The client lists 28 Tomba tools.
  2. Ask the assistant to run the list_flags tool. A list of flags, even an empty one, means your credentials work.

When the server starts over stdio, it writes Tomba MCP server running on stdio to its error output. Claude Desktop saves that output in mcp-server-tomba.log, in ~/Library/Logs/Claude on macOS and %APPDATA%\Claude\logs on Windows.

HTTP transport

With --transport http, the server listens on the given port and serves Streamable HTTP at /mcp, with a health check at /health:

TerminalCode
TOMBA_API_KEY="ta_xxxx" TOMBA_SECRET_KEY="ts_xxxx" \ npx -y @tomba-io/tomba-mcp-server --transport http --port 3000

Clients connect to http://localhost:3000/mcp. The server handles one MCP session per process: a second client, or a client that reconnects, gets HTTP 500 until you restart the server.

In HTTP mode, the server doesn't authenticate clients, listens on every network interface, and accepts requests from any web page origin. Anyone who can reach the port can use your Tomba credits. Run it only where the port is closed to other machines, or use stdio.

Troubleshooting

SymptomWhat to do
SyntaxError: Unexpected token 'with' at startupUpgrade Node.js to 18.20 or later. The client runs the node found on its own PATH, which can differ from your terminal's.
Error: TOMBA_API_KEY and TOMBA_SECRET_KEY environment variables are requiredSet both variables in the env block of the client configuration.
The tools are listed, but every call returns an authentication errorThe server checks credentials only when a tool calls the API. Check the key and secret, and whether the key has expired: see Key expiry.
A call fails with a rate limit errorThe local server doesn't retry failed requests. Wait, then call again; see Handle 429 responses.
Last modified on October 7, 2026
Tools referenceDocs for AI assistants
On this page
  • Requirements
  • Run the server
  • Configure a client
    • Claude Desktop
    • Claude Code
    • VS Code
    • Zed
  • Verify the connection
  • HTTP transport
  • Troubleshooting
JSON
JSON
JSON