Integration

Tomba integration

Tomba finds, verifies and enriches professional B2B email addresses and phone numbers. Find the emails at a company domain, a person's email from their name, the author of an article or the owner of a LinkedIn profile; verify an address; enrich an email or a domain into person and company profiles; find and validate phone numbers; search companies by filters or a plain-language query; read a domain's email count, email format, locations, technologies and similar companies; save leads and read leads, lead lists and lead attributes; create bulk jobs over lists of values, follow them and download their CSV results; and read credit usage, rate limits and billable lookups. Not exposed: updating or deleting leads, managing lead lists and attributes, launching, cancelling, retrying or deleting an existing bulk job (create one with launch set to true), data-error reports, API key management, the bulk webhook secret, CSV file upload and the MCP endpoint. Authentication is an API key and its secret, sent in the X-Tomba-Key and X-Tomba-Secret headers.

Connect Tomba How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Tomba.Built from the 37 Tomba tools below, on the connection you add once.

What you can do with Tomba

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Bulk, 3 operations

create_bulk_jobCreate bulk jobPOSTCreates a bulk job of the given type from a list of values (list) or rows with a header (data). Set launch to true to start it at once; otherwise it stays pending. Nothing is charged until the first download.
get_bulk_jobGet bulk jobGETGet a job by ID, with its options in `config`, its results in `metrics`, and, once it is billed, the first result rows in `preview`.
list_bulk_jobsList bulk jobsGETList the jobs of a type, `limit` per page, sorted by job ID. Jobs are shared by all members of a workspace. Archived jobs are listed only with `archived=true`, and deleted jobs never.

Find, 3 operations

enrich_companyEnrich companyGETReturns the company behind a domain in Clearbit's Company API format: name, description, location, industry codes, social handles, size, revenue, and technologies.
enrich_personEnrich personGETReturns the person behind an email address in Clearbit's Person API format: name, location, employment, and social profiles.
enrich_person_and_companyEnrich person and companyGETReturns the person behind an email address and the company behind its domain in one call, in Clearbit's format.

Lead, 3 operations

create_leadCreate leadPOSTSaves a lead to your account. Every field is optional, `email` included. Tomba doesn't check for duplicates: saving the same email address twice creates two leads. - `list_id` must be a JSON number.
get_leadGet leadGETReturns one lead of your workspace, as the only item of `data.leads`. A lead that doesn't exist, or that you can't see, returns `200` with an empty `data.leads` array, not `404`. Also accepts an OAuth 2.0 access token with the `leads` scope.
list_leadsList leadsGETReturns the leads of your workspace, or your own leads when you aren't in a workspace, with each lead's list and custom attribute values. - `list` returns only the leads in one list.

Leads list, 2 operations

get_lead_listGet lead listGETReturns one lead list of your workspace. Also accepts an OAuth 2.0 access token with the `leads` scope.
list_lead_listsList lead listsGETReturns up to 25 lead lists of your workspace, or your own lists when you aren't in a workspace. There's no pagination. Also accepts an OAuth 2.0 access token with the `leads` scope.

Attribute, 1 operation

list_attributesList attributesGETReturns up to 25 custom lead attributes of your workspace, or your own attributes when you aren't in a workspace. There's no pagination. Use an attribute's `identifier` as the key when you set its value in a lead's `attributes`.

Author finder, 1 operation

find_author_emailFind author emailGETFinds the email address of the author of an article or blog post from its URL. Tomba reads the page, identifies the author, and returns their address with the article and every author candidate in `data.info`.

Domain search, 1 operation

search_domain_emailsSearch domain emailsGETReturns the company behind a domain and one page of the email addresses Tomba has for it, with each person's name, job title, department, and verification status.

Domain status, 1 operation

get_domain_statusGet domain statusGETTells you whether a domain, or the domain of an email address, belongs to a webmail provider such as Gmail or to a disposable email provider. The endpoint needs no API key, isn't charged, and isn't rate-limited. Send `domain` or `email`.

Domain suggestion, 1 operation

suggest_domainsSuggest domainsGETReturns up to five companies whose name or domain matches your query, with their domain and the number of email addresses Tomba has for it. Use it to turn a company name into a domain before a domain search.

Download, 1 operation

download_bulk_jobDownload bulk jobGETDownloads a result file of a completed bulk job as CSV text: file=full (every result, the default), valid (rows with a valid result) or not_found (input rows with no result). The first download charges the job's credits; later downloads are free.

Email count, 1 operation

get_email_countGet email countGETReturns how many email addresses Tomba has for a domain, by email type, department, and seniority. Use it to size a domain before a domain search. An unknown, webmail, or disposable domain returns `0` in every count.

Email finder, 1 operation

find_emailFind emailGETFinds a person's professional email address from their name and their company's domain or name. Tomba returns a stored address when it has one; otherwise it generates candidate addresses and checks them against the company's mail servers.

Email format, 1 operation

get_email_formatGet email formatGETReturns the formats that a domain's email addresses follow, such as `{first}.{last}`, with the share of known addresses that use each one. `data` is an empty array when Tomba has no formats for the domain.

Email source, 1 operation

get_email_sourcesGet email sourcesGETReturns the public web pages where Tomba found an email address, with when it was first and last seen on each. When Tomba has no sources for the address, the response has status `201` and an empty `data` array. This endpoint uses the sources balance.

Email verifier, 1 operation

verify_emailVerify emailGETChecks whether an email address can receive mail. data.email.status and data.email.result give the outcome; the other fields report the individual checks (format, MX records, SMTP, catch-all, webmail, disposable).

Enrich, 1 operation

enrich_emailEnrich emailGETReturns the person behind an email address, with their name, company, job title, social profiles, and the address's verification status, in Tomba's own format.

Estimate, 1 operation

estimate_bulk_jobEstimate bulk jobGETGet the credits a job costs, and whether your balance covers them. Before the job completes, `basis` is `upper_bound`: the cost if every row returned the maximum. Once it completes, `basis` is `exact`: what the first download charges.

Linkedin, 1 operation

find_linkedin_emailFind linkedin emailGETFinds the professional email address of the person behind a LinkedIn profile URL. Tomba returns a stored address when it has one; otherwise it may read the profile and search for the address live.

Location, 1 operation

get_email_locationsGet email locationsGETReturns, for each country, how many of a domain's email addresses belong to people in that country. To list the addresses for one country, pass its code to domain search in `country`.

Log, 1 operation

list_logsList logsGETReturns your billable lookups, newest first, with what each one cost. Only requests to endpoints that cost credits, and that returned `200` with a result, are logged.

Me, 1 operation

get_accountGet accountGETReturns your account and plan, with your search, verification and email count allowances and what you have used in the current usage window. Your API secret is not returned by this tool.

Phone finder, 1 operation

find_phoneFind phoneGETFinds phone numbers for a person or a company from an email address, a domain, or a LinkedIn profile URL. Send at least one of `email`, `domain`, and `linkedin`; you can combine them, and the numbers found for each are merged without duplicates.

Phone validator, 1 operation

validate_phoneValidate phoneGETChecks whether a phone number is valid in its country's numbering plan and returns its formats, line type, carrier, region, and time zones.

Progress, 1 operation

get_bulk_job_progressGet bulk job progressGETGet a job's status, progress, estimated time left, and results so far. The fields are at the top level of the response, not in `data`.

Rate limit, 1 operation

list_rate_limitsList rate limitsGETReturns, for every rate-limited route, the limits that apply to your account and the requests counted against them in the current minute and day. - The limits come from your plan, raised by any credit pack that still has credits. `0` means unlimited.

Search, 1 operation

search_companiesSearch companiesPOSTSearches Tomba's company database with structured filters or a natural-language query, and returns 50 companies per page. When you send `query`, filters are generated from it with an AI model and any `filters` you send are ignored.

Similar, 1 operation

find_similar_companiesFind similar companiesGETReturns companies similar to a domain, such as competitors, 25 per page. When Tomba has the domain on record but no similar companies stored, it looks them up live before it responds, except on the Free plan.

Technology, 1 operation

get_domain_technologiesGet domain technologiesGETReturns the technologies detected on a domain's website, such as its analytics, live chat, and payment tools, with their categories. When Tomba hasn't analyzed the domain before, it detects them live before it responds, except on the Free plan.

Type, 1 operation

list_bulk_typesList bulk typesGETList every bulk type with its input fields and the header names detected for them, its options, row limit, daily limits, result files, and metrics distributions.

Usage, 1 operation

get_usageGet usageGETReturns your daily credit usage over a range of days, one row per user and day, with totals for the range. - `duration` sets the range: from that many days ago through today. Rows exist only for days with charged credits.

Use Tomba from Claude Code, Cursor or Codex

Connect Tomba in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Tomba operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Tomba

Create your workspace
Sign up free. Nothing to install.
Connect Tomba once
Add your Tomba connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.