Claude Tomba connectorWhat Claude can do in your Tomba account.
The Claude Tomba connector exposes 11 tools. 11 read, 0 write: all of them look things up in Tomba's contact data. Below, what Claude can find for you, what each lookup costs you in Tomba credits, and the local setup this desktop extension needs.
Verified Trustpilot reviews · AI, automation & growth agency
What it changes for sales and prospecting
Instead of switching to Tomba, pasting a domain or a name and copying results back, you ask Claude. It picks the right lookup, runs it against your Tomba account, and puts the answer in the conversation. Everything on the list reads data; nothing on the sheet creates or edits records.
Build a contact list for one account. email_count tells you how many addresses Tomba knows for a domain, then domain_search brings them back.
Clean before you send. email_verifier checks whether an address can receive mail, and phone_validator does the same job for numbers.
Widen the funnel. similar_finder suggests lookalike companies and technology_finder shows what their site runs on, so you can qualify them before any outreach.
Put a name on a byline or a profile. author_finder and linkedin_finder turn an article or a LinkedIn page into an address you can write to.
What it will not do: send anything, or add a lead to Tomba. The sheet exposes reading only. It also does not run by itself: Claude calls these tools while it answers you, never on a schedule or when a form comes in. For that kind of hands-off enrichment, an automation tool does a different job; the Integrations hub gathers that side. Keep in mind each call spends Tomba credits, like the API request behind it.
The vocabulary in one minute
Five words you will meet while setting Tomba up.
- Connector
- The link you set up once between Claude and an account you already hold, so Claude can use it while answering.
- Tool
- A single named action the connector gives Claude. Claude decides which to call; the directory sheet lists every one.
- Authorization
- The step where you hand Claude access to the service. Here it takes your Tomba key and secret, set once on your computer.
- Approval
- The confirmation Claude waits for before finishing an action that changes your account, shown in the chat when relevant.
- MCP
- The open standard connectors rely on, which is what lets an assistant like Claude talk to an outside service.
Plug Tomba into Claude in three steps
- 01
Find Tomba in Claude Desktop
This one is a desktop extension, so it lives in Claude Desktop. In the settings, open Customize, then Connectors, and look for Tomba. On a Team or Enterprise workspace, an Owner or Primary Owner enables it first.
- 02
Start the connection
Click Connect on its row. Tomba then needs your account credentials, an API key and its secret, read from your computer. If it breaks later, use Disconnect and add it again.
- 03
Check what the access covers
The key you provide decides what Claude can reach, and every lookup runs on that Tomba account. Access can also be withdrawn from the Tomba account itself.
The 11 tools, sorted by what they do
Tomba MCP Server gives Claude 11 tools: 11 that read your account, 0 that change something in it.
One group only: every tool reads. Names stay as Claude shows them, in English.
- 11 read
What Claude reads (11)
11 toolsEleven lookups in Tomba's contact and company data. None changes your account.
domain_search
Pulls the email addresses Tomba holds for a company, from its domain or its name, so Claude can hand you a first list of contacts at that organisation.
email_finder
Works out a person's email address from their name and the company they work for.
email_verifier
Tells you whether a given email address can actually receive mail.
email_enrichment
Starting from an email address, returns the person and the company behind it.
author_finder
Give it the link to an online article and it finds the email address of the person who wrote it, so the byline turns into someone you can actually contact.
linkedin_finder
Point it to a LinkedIn profile and it returns the email address Tomba associates with that person, when Tomba has one on file.
phone_finder
Looks for phone numbers starting from whatever you already hold: an email address, a company domain or a LinkedIn profile. Claude passes the one you gave and reports what Tomba finds.
phone_validator
Checks that a phone number is valid before anyone dials it or loads it into a tool.
email_count
Counts how many email addresses Tomba knows for a domain, without listing them. A quick number before deciding whether the full search is worth it.
similar_finder
Takes a company domain and suggests other companies that resemble it, which gives you a starting point when your prospect list runs dry.
technology_finder
Reads a website from the outside and lists the technologies it runs on, as far as Tomba can see them.
What Claude asks before acting
By default, Claude stops and asks for your go-ahead before any action it takes on an account for you. On this sheet every tool reads, so those prompts should hardly come up.
On a Team or Enterprise workspace, owners decide whether a member may let some actions through without being asked each time. They can also cap what a connector may do across the organization, reading allowed and writing closed, for example, and nobody lifts that from their own account. Claude works with the rights of the Tomba account whose key you entered and nothing beyond. Remember that reading still has a cost: each lookup is billed in credits.
Which plans it is available on
None of the 819 sheets in the official directory shows availability per plan. The answer for a given connector is not published anywhere, and that is a real gap in the catalogue.
The general rule is public: desktop extensions install on Claude Desktop, and remote connectors are open to every user on Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner enables a connector before members can use it. For the current state, the connector's sheet in the official directory is the place to check. Tomba is documented only by its publisher.
Where this connector stops
A connector is not an automation. Claude calls these tools while it answers you: nothing enriches a new lead on its own when it lands in your CRM.
A list that only reads is an observed floor, not a guarantee: an administrator can open actions that appear on no public sheet. The partner badge is not a security audit, and Anthropic states on every sheet that it neither chooses a publisher's tools nor guarantees how they behave. Plug in only what you trust. Other pages in the family, such as the Claude activecampaign connector, show what a connector with write tools looks like.
Need help connecting Tomba MCP Server to Claude?
A person reads every message.
