Tomba MCP Server

The Tomba MCP Server is the official Model Context Protocol integration for Tomba.io, a B2B email finder and verification platform. It lets AI agents call Tomba's APIs through a standardized interface to discover professional email addresses, verify deliverability, enrich contacts, and pull related company and phone data.

The server exposes 12 tools covering the most common prospecting workflows: domain-wide email search, name-and-domain email guessing, email verification, contact enrichment, author and LinkedIn email lookups, phone discovery and validation, technology stack detection, similar-company finding, and natural-language company search. It is written in TypeScript and can be run via npx, or built from source and run over stdio (default) or HTTP transport.

Because it is maintained by Tomba.io itself, the tool surface tracks the official REST API, and authentication uses the same API key plus secret key pair that the Tomba dashboard issues. It is a good fit for sales, recruiting, and growth workflows where an agent needs to enrich a list of domains or people without leaving the chat.

Tools

Prerequisites

• Node.js 18 or higher
• A Tomba.io account with API access
• Your TOMBA_API_KEY and TOMBA_SECRET_KEY from the Tomba dashboard under API settings

Option 1: NPX (recommended)

Add the server to your Claude Desktop config (~/Library/Application Support/Claude/claude_desktop_config.json on macOS, %APPDATA%\Claude\claude_desktop_config.json on Windows):

{
  "mcpServers": {
    "tomba": {
      "command": "npx",
      "args": ["-y", "tomba-mcp-server"],
      "env": {
        "TOMBA_API_KEY": "your-api-key-here",
        "TOMBA_SECRET_KEY": "your-secret-key-here"
      }
    }
  }
}

Restart Claude Desktop (or your MCP client) to pick up the new server.

Option 2: Build from source

git clone https://github.com/tomba-io/tomba-mcp-server.git
cd tomba-mcp-server
yarn install
yarn build

Then point your MCP client at the built entry script using its absolute path, with the same TOMBA_API_KEY and TOMBA_SECRET_KEY env vars.

Transport options

The server defaults to stdio. It also supports HTTP transport (for example --transport http --port 3000) for clients that prefer a network connection.

• Enrich a list of company domains with verified contact emails and the people behind them before an outbound campaign.
• Given a first name, last name, and company website, guess the most likely email and verify it in one chat turn.
• Pull the author email for a list of article URLs to build a journalist or content outreach list.
• Convert LinkedIn profile URLs into emails and phone numbers for sales follow-up.
• Run natural-language company searches (for example, "Series B fintech in Germany") and qualify each result with technology stack and similar-company data.

• "Find all emails at stripe.com and verify which ones are deliverable."
• "Get the most likely email for Jane Doe at acme.com, then enrich it with job title and social profiles."
• "Here are 10 LinkedIn URLs, find emails and phone numbers for each."
• "What technology stack does shopify.com use, and find 5 similar companies."
• "Search for B2B SaaS companies in the US with 50-200 employees and return their domains."

• Official server maintained by Tomba.io, so the tool surface tracks the underlying API.
• Broad coverage: 12 tools spanning email, phone, company, and technology lookups.
• Simple npx install with no need to clone or build, and supports both stdio and HTTP transports.

• Requires a Tomba.io account and API credits; free tier limits apply.
• All tools are read-only lookups, no campaign or list-management actions.
• Quality of results depends entirely on Tomba's underlying data coverage for a given domain or person.

• Hunter.io MCP for email finding and verification with a similar API model.
• Apollo.io integrations via community MCP servers for broader B2B contact and company data.
• Clearbit (now part of HubSpot) for enrichment-focused workflows where company firmographics matter more than email discovery.