Skip to content
Tomba home
Start free

// ai & llm

Tomba Remote MCP

the Remote MCP Server powered by Tomba.io, a comprehensive Model Context Protocol (MCP) server that provides advanced email discovery, verification, and enrichment capabilities through a streamlined HTTP transport interface.

View IntegrationSetup Guide
Official Integration
  1. 01
    mcp email finderIn Tomba Remote MCPAI & LLM
  2. via mcp server
  3. 02

    MCP tool email_finder

    GET/email-finder1 search credit
  4. 03

    Result

    richard@piedpiper.comvalid

// 01 · overview

Tomba in Tomba Remote MCP

Remote MCP Server

The Tomba Remote MCP Server provides email intelligence capabilities to AI applications through a cloud-hosted Model Context Protocol server. No local installation required - connect directly via HTTP.

Remote vs Local MCP

Remote MCP (this integration):

  • Cloud-hosted - no installation needed
  • HTTP/SSE transport
  • Perfect for web applications
  • Managed and maintained by Tomba
  • Always up-to-date

Local MCP:

  • Runs on your machine
  • Stdio transport
  • Better for desktop AI apps
  • More control over execution

Features

  • Cloud-Hosted: No setup or maintenance required
  • HTTP API: Simple RESTful integration
  • Real-Time: Server-Sent Events for streaming
  • Scalable: Handles high request volumes
  • Secure: API key authentication

Available Tools

The remote MCP server provides these capabilities:

  • Email Finder by name and domain
  • Email Verifier for deliverability checking
  • Domain Search for company emails
  • Email Enrichment for detailed data
  • LinkedIn Email Finder
  • Author Finder from URLs

Connection Setup

Connect to the remote MCP server using HTTP transport:

const client = new MCPClient({
  transport: 'http',
  url: 'https://mcp.tomba.io',
  headers: {
    'X-API-Key': 'your-tomba-api-key',
    'X-API-Secret': 'your-tomba-api-secret'
  }
})

Compatible Clients

  • Web-based AI applications
  • Browser extensions
  • Mobile apps
  • Serverless functions
  • Any HTTP-capable client

Use Cases

  1. Web Applications: Add email intelligence to web apps
  2. Browser Extensions: Build AI-powered email finders
  3. Mobile Apps: Integrate email discovery in iOS/Android
  4. Serverless: Use in Lambda, Vercel, or Cloudflare Workers
  5. API Gateways: Proxy AI requests through your API

Authentication

Authentication uses API key and secret in request headers:

X-API-Key: your_api_key
X-API-Secret: your_api_secret

Documentation

Full API reference and integration guides available at Tomba MCP Documentation.

Support

// 02 · endpoints

The API behind Tomba for Tomba Remote MCP

Integrations call the same Tomba endpoints as your code, with your account's credits. Each call costs what its endpoint costs.

01GET/email-finder1 search credit02GET/people/find1 search credit03GET/enrich1 search credit04GET/linkedin1 search credit05GET/email-verifier1 verification credit

// customers

What teams say about Tomba

  • The data is always fresh, and the n8n integration is excellent for my use case. Support is very responsive overall. I'd rate it 9/10.
    Benjie MalinaoCo-Founder & CTO, Channel Automation
  • Tomba is my favorite tool for lead finding and verification because it gets the job done. … Heck, you can even export your prospects from tomba to your favourite CRM like Hubspot directly or to other CRM's via Zapier, Pabbly, or Integrately if you like!
    KC W.Chief Executive Officervia G2

// quick start

Make your first call in a minute

Free account, real API key, the same endpoints Enterprise customers use.

  1. 1Create a free account25 searches a month. No card.
  2. 2Copy your key and secretFrom API keys in the dashboard.
  3. 3Call the APIPaste the request; the answer is JSON.
Get free API keyRead the docs
curl "https://api.tomba.io/v1/email-finder?domain=piedpiper.com&first_name=Richard&last_name=Hendricks" \
  -H "X-Tomba-Key: $TOMBA_API_KEY" \
  -H "X-Tomba-Secret: $TOMBA_SECRET_KEY"
Response
200 OK· 1 search credit
{
  "data": {
    "email": "richard@piedpiper.com",
    "first_name": "Richard",
    "last_name": "Hendricks",
    "full_name": "Richard Hendricks",
    "website_url": "piedpiper.com",
    "company": "Pied Piper",
    "pattern": "{first}",
    "department": "executive",
    "type": "personal",
    "position": "CEO",
    "country": "US",
    "gender": "male",
    "twitter": null,
    "linkedin": "https://www.linkedin.com/in/richard-hendricks",
    "score": 100,
    "accept_all": false,
    "phone_number": true,
    "verification": {
      "date": "2025-01-15T10:32:00+01:00",
      "status": "valid"
    },
    "sources": [
      {
        "uri": "https://piedpiper.com/blog/engineering",
        "website_url": "piedpiper.com",
        "extracted_on": "2024-06-01T09:14:07+01:00",
        "last_seen_on": "2025-01-10T17:02:44+01:00",
        "still_on_page": true
      }
    ],
    "phone_data": []
  }
}