What is the Model Context Protocol (MCP)?

MCP is an open standard that lets AI assistants connect to external tools and data sources. Think of it as a USB port for AI tools. Instead of copy-pasting data between Tomba and your AI assistant, MCP creates a direct connection so the AI can call Tomba's API on your behalf.

How do I set up the Tomba MCP server?

Add the remote URL https://mcp.tomba.io/mcp to your AI tool's MCP config. Claude Desktop uses OAuth: authorize in your browser, with no API keys needed. For Cursor, VS Code, Windsurf, and other clients, use a Bearer token (base64 of key:secret) or X-Tomba-Key/Secret headers.

Which AI tools support MCP?

Claude Desktop, Claude Code, ChatGPT, VS Code, Cursor, Windsurf, Zed, Gemini CLI, Cline and any client that implements the MCP specification. Connect a client has the setup for each.

Does using MCP cost extra credits?

No. A tool call is billed exactly like the API request it makes, against your plan's credits: an email finder call costs 1 search credit when it returns an address, a verification 1 verification credit, account and lead tools nothing. There is no extra charge for MCP. See Credit costs .

Are my API keys secure with MCP?

With OAuth (Claude Desktop), you never handle API keys directly: authorization happens in your browser. For Bearer token or header auth, credentials are stored locally in your MCP config and sent only to the Tomba MCP server at mcp.tomba.io.

What Tomba tools are available via MCP?

The MCP server exposes 28 tools including domain search , email finder , email verifier , person/company/combined enrichment, email sources, email format, domain status, author finder, LinkedIn finder, phone finder, phone validator, technology finder, similar finder, companies search, autocomplete, location, account management, and more. Plus 3 resources (API status, department list, API documentation) and 12 built-in prompts for workflows like lead research, competitor analysis, ABM campaigns, and due diligence.

What are the rate limits when using MCP?

Tool calls count toward your plan's API rate limits (for example 1 request per second on the Free plan; Pro Plus, Scale and Enterprise have no per-second limit). The MCP server has no limit of its own and doesn't pass rate limit headers to the client. See Rate limits .

Can I use MCP for bulk operations?

Yes. You can ask your AI assistant to process multiple lookups in a single conversation. The MCP server handles sequential API calls automatically, respecting rate limits between requests.

// ai integration

Connect Tomba to AI tools via MCP

Connect Tomba to Claude, Cursor, VS Code, ChatGPT and any other MCP client. OAuth for Claude Desktop, so no API keys are needed. Remote server at mcp.tomba.io, no local install required.

Get started View on GitHub

https://mcp.tomba.io/mcp28 toolsOAuth or API key

Agent with Tomba connectedmcp.tomba.io/mcp

You: Find the engineers at Pied Piper

Calling tooldomain_search

tools/call

{
  "name": "domain_search",
  "arguments": { "domain": "piedpiper.com", "department": "engineering" }
}

// structuredContent · data.emails[0]

dinesh@piedpiper.comSoftware Engineer valid

// 01 · connect

One URL, nothing to install

Add https://mcp.tomba.io/mcp to your client. Clients that support MCP authorization sign you in with OAuth; the others send your key and secret.

Claude Code

// Setting: claude mcp add
// Authentication: OAuth · API key headers

claude mcp login opens a browser window where you sign in to Tomba. With headers, the shell expands the variables when you run the command.

Claude Code

claude mcp add --transport http --scope user tomba https://mcp.tomba.io/mcp
claude mcp login tomba

claude mcp add --transport http --scope user tomba https://mcp.tomba.io/mcp \
  --header "X-Tomba-Key: $TOMBA_API_KEY" \
  --header "X-Tomba-Secret: $TOMBA_SECRET_KEY"

Setup for every client

// 02 · tools

28 tools, each one API call

Every tool call is one request to the Tomba API with your credentials, billed like that request. Two tools change data; the others are read-only.

domain_search

read-only

Email addresses Tomba has for a company

// Calls: GET/v1/domain-search
// Cost: 1 search credit per 10 resultsAt least one address is returned. 1 credit per 10 results requested with limit.

tools/call · domain_search

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "domain_search",
    "arguments": {
      "domain": "piedpiper.com",
      "department": "engineering"
    }
  }
}

Every tool's parameters

// 03 · access

Three ways to authenticate

With OAuth, each tool needs the scope of the endpoint it calls: read, search, verify, enrich, leads or account. Review or revoke access under Connected apps in the dashboard.

OAuth 2.0

Clients that support MCP authorization open a browser window where you sign in to Tomba and approve access. You don't handle keys.

// The client sends

Authorization: Bearer <access token>

// Tools: All tools except usage_info and get_logs
// Clients: Claude Code, Claude Desktop, ChatGPT, VS Code, Windsurf, Zed, Gemini CLI

API key as a bearer token

For clients that can send an Authorization header but not custom headers: your key and secret, separated by a colon, in base64.

// The client sends

Authorization: Bearer <base64 of key:secret>

// Tools: All tools
// Clients: Zed

API key headers

Your key and secret in the same headers as the Tomba API.

// The client sends

X-Tomba-Key: ta_xxxx
X-Tomba-Secret: ts_xxxx

// Tools: All tools
// Clients: Claude Code, Cursor, VS Code, Windsurf, Gemini CLI, Cline

// 04 · faq

Frequently asked questions

Still have questions? Visit the help center

Connect Tomba to AI tools via MCP

One URL, nothing to install

28 tools, each one API call

Three ways to authenticate

OAuth 2.0

API key as a bearer token

API key headers

Frequently asked questions

See who Tomba finds at any company