# tomba-io/tomba-mcp-server [Health: Active]

**Category:** 🎯 Marketing  
**Repository:** https://github.com/tomba-io/tomba-mcp-server  
**GitHub Stars:** 8  
**npm Downloads (last month):** 323  
**Views:** 3  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/tomba-io-tomba-mcp-server

## Description
Email discovery, verification, and enrichment tools. Find email addresses, verify deliverability, enrich contact data, discover authors and LinkedIn profiles, validate phone numbers, and analyze technology stacks.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "tomba-mcp-server": {
    "command": "npx",
    "args": ["-y","will"],
    "env": {
      "TOMBA_API_KEY": "",
      "TOMBA_SECRET_KEY": ""
    }
  }
}
```

**Requires environment variables:** `TOMBA_API_KEY`, `TOMBA_SECRET_KEY` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## What tomba-io/tomba-mcp-server MCP server does

The tomba-io/tomba-mcp-server MCP server connects an MCP-compatible client to the Tomba.io API. Its capabilities cover contact discovery, email validation, enrichment, company research, and domain analysis. The API account supplies the underlying data, while the MCP layer makes those operations available to an agent through standardized tools, resources, and prompts.

Email-focused operations include searching a domain for addresses, generating a likely address from a person and domain, finding authors or LinkedIn contacts, checking email sources and domain patterns, and counting addresses. Verification can check deliverability and whether an address appears in Tomba’s database. Enrichment tools return available person or company details, including items such as role, social profiles, industry, company size, and location.

Additional operations cover phone lookup and validation, disposable or webmail domain checks, company-name autocomplete, similar-domain discovery, technology-stack detection, employee location counts, natural-language company search, lead management, account information, usage, API keys, flags, and request logs.

## How it works

The server exposes 28 tools, seven URI resources, and 16 pre-built prompts. Resources provide addressable views such as `tomba://email/{email}`, `tomba://domain/{domain}`, similar-domain results, technology information, API status, and documentation. Prompts organize multi-step activities including contact finding, list verification, lead enrichment, journalist research, competitor analysis, technology audits, market research, and company targeting.

stdio is the default transport and is intended for local MCP client configuration. An HTTP mode is also available and provides REST endpoints. API requests use live Tomba infrastructure. Calls have a 120-second timeout, and the server retries rate-limit and server-error responses up to three times with delays of one, two, and four seconds.

## Setup and configuration

Running the tomba-io/tomba-mcp-server MCP server requires Node.js 18 or newer, npm or Yarn, and a Tomba API account. The published package is `@tomba-io/tomba-mcp-server`; the README notes that it replaced the older `tomba-mcp-server` package name.

For a stdio setup, run the package with `npx -y @tomba-io/tomba-mcp-server` and provide these environment variables:

- `TOMBA_API_KEY`: the Tomba API key.
- `TOMBA_SECRET_KEY`: the Tomba secret key.

The README shows this configuration for Claude Desktop on both macOS/Linux and Windows. Source installation is also documented: clone the repository, run `yarn install`, and build with `yarn build`.

## Tools and capabilities

Use the discovery tools to locate addresses by domain, name, article author, or LinkedIn URL. Use verification and validation tools before relying on email or phone contact data. Enrichment operations can combine person and company information, while company search supports natural-language queries and filters for size, type, revenue, and industry.

Account and operational tools expose plan, credit, usage, submitted data flags, leads, API keys, and recent request logs. The service documents plan-based rate limits: the free plan allows one request per second, two per minute, and five per day, while higher plans provide larger limits. Requests that produce no result do not consume credits, and duplicate requests within 30 days are not counted again.

## Limitations and notes

The tomba-io/tomba-mcp-server MCP server depends on a Tomba account and its API credentials. Results and response times depend on the target company’s SMTP server, website responsiveness, and the requested catch-all detection depth. Rate limits vary by Tomba plan and endpoint, so bulk workflows should account for those limits.

The supplied material explicitly documents Claude Desktop configuration and stdio operation. It does not establish compatibility with every other MCP client. The README also mentions an OpenClaw skill in the repository, but the provided excerpt does not document its full behavior or configuration.

_Full upstream README: https://allmcps.com/mcp/tomba-io-tomba-mcp-server/readme_