Sales & Customer Support · Tomba + Claude
Tomba MCP with Claude: Find and Verify B2B Sales Contacts Faster
The short answer
Claude works with Tomba through the Model Context Protocol (MCP), an open standard that acts as a secure adapter between the two. Once connected with an API key, Claude can look up business email addresses, verify contacts and enrich lead records. The organisation controls which actions are allowed, and people approve anything that reaches customers.
What is Tomba?
Tomba is an email finder built for B2B sales and email marketing. It helps teams find professional email addresses for people at companies and check whether those addresses are valid before outreach begins. Sales development representatives, account managers, marketing teams and founders typically use it to build and clean prospect lists. It also supports lead enrichment, adding useful business details to existing contact records.
How Claude connects to Tomba through MCP
The Model Context Protocol (MCP) is an open standard that lets Claude securely use other software, reading information and taking actions with permissions the organisation controls. Think of it as a universal adapter between Claude and the tool. Tomba provides MCP access alongside its direct API, so Claude can reach Tomba without custom coding for each request.
Once connected, Claude can typically look up professional email addresses for a given name and company, verify whether contacts appear deliverable, and enrich lead records with business information. Your team can make these requests in plain language, such as asking Claude to find the marketing director at a named company and check the address.
Permissions and approvals keep people in charge. Access is set up using the API key, with least-privilege settings so Claude only reaches what the workflow needs. Consequential steps, such as adding contacts to a campaign, can require a person's sign-off before anything happens.
What you can automate
Building targeted prospect lists
A sales development representative describes the ideal buyer, such as heads of operations at mid-sized logistics firms. Claude uses Tomba to find matching contacts and returns a clean list with company names and roles. The rep reviews the list before it moves to the CRM, saving hours of manual searching each week.
Verifying contacts before a campaign
Email marketing teams often inherit old or uncertain lists. Claude can check each address through Tomba's verification and flag those that appear risky or undeliverable. Cleaner lists typically mean fewer bounces and a better sender reputation, which helps future campaigns reach the inbox.
Enriching leads from inbound enquiries
When a web form arrives with only a name and company, Claude can use Tomba to find a verified work email and add business details. The enriched record is then passed to the sales team, so the first follow-up is faster and better informed.
Preparing account research for key deals
Account managers preparing for an important meeting can ask Claude to gather the right contacts across a target company. Tomba supplies verified addresses and roles, and Claude summarises who the decision makers are. The result is a short briefing that helps the team plan outreach to the right people.
Keeping the CRM current
Contact data goes stale as people change jobs. Claude can review records in a scheduled run, use Tomba to confirm details, and suggest updates for a manager to approve. This keeps the customer database accurate without relying on someone to check each entry by hand.
An end-to-end workflow: Inbound lead enrichment and routing
TriggerA new enquiry is submitted through the website contact form.
Claude reads the enquiry and identifies the person's name and company.
Claude uses Tomba to find and verify a professional email address for that person.
Claude adds business details to the lead record in the CRM.
Claude scores the lead against the ideal customer profile and suggests an owner.
The sales manager approves the assignment, and the lead is routed to the right representative.
The representative receives a summary and a verified contact to follow up within the hour.
OutcomeTypically, leads are enriched and routed within minutes rather than days, with fewer incomplete records and faster first contact.
How we set it up
Free automation audit
We review your sales and marketing processes to find the contact-finding and list-building tasks worth automating. You receive a clear list of priorities at no cost.
Secure connection with an API key
We connect Claude to Tomba using your API key, stored securely with least-privilege access. You stay in control of what the connection can reach, and the key can be rotated at any time.
Workflow design across your systems
We design the end-to-end process across Tomba, your CRM, Microsoft 365 and any other tools you use. Approval points are placed wherever a person should review an action.
Testing and launch with monitoring
We test the workflow against real past leads and lists, then launch with activity logs and monitoring so every action can be reviewed.
Team training
We train your sales, marketing and operations staff to use Claude with Tomba confidently, including how to review outputs and handle exceptions.
Who benefits
- Sales development leaders
- Faster access to targeted, verified prospect lists for their team.
- Marketing managers
- Cleaner contact lists that support better campaign deliverability.
- Account executives
- Quicker research on key contacts before important meetings.
- Revenue operations teams
- Fewer stale records and more consistent data across the CRM.
Security and control
- Access is limited to the permissions the workflow needs, using least-privilege settings.
- Your Tomba API key is stored securely and can be rotated or revoked at any time.
- People approve consequential actions, such as adding contacts to campaigns or changing CRM records.
- Activity logs record what Claude requested and returned, supporting review and audit.
- Outreach remains subject to your own compliance checks and the anti-spam rules that apply to your market.
For teams in the US, UK, India and the Middle East
Organisations in the United States and the United Kingdom must follow rules on commercial email, including consent and opt-out requirements. In India, the Digital Personal Data Protection Act, 2023 governs how personal data is handled. Companies in the UAE and Saudi Arabia must comply with their national data protection laws. We choose a hosting region for any custom application to meet these requirements, whether in India, the United States, the United Kingdom or the European Union.
Learn more about Claude and MCP
Anthropic's AI model and assistant.
Secure links between Claude and business tools.
How engineers build and change software with Claude.
Hosted agents that run multi-step work.
The open standard Claude uses to connect to tools.
Frequently asked questions
What does the Tomba MCP server do?
The Tomba MCP server lets Claude use Tomba's capabilities, such as finding business emails and verifying contacts, through a standard secure connection. Instead of building a custom integration for every request, your team can ask in plain language and Claude carries out the lookup. Access is controlled by the permissions you set.
Is connecting Tomba to Claude secure?
Security depends on how the connection is configured. We use your Tomba API key with least-privilege access, store it securely, and limit Claude to the actions your workflow requires. Activity logs and approval steps allow your team to review what happened. We also check that the setup meets your internal security policies.
What can Claude do with Tomba once connected?
Typically, Claude can find professional email addresses for a named person and company, verify whether addresses appear deliverable, and enrich lead records with business information. It can then pass results to your CRM or summarise them for your team. Consequential actions can be set to require human approval.
How long does setup take?
Many straightforward connections can be set up and tested within a few days. More involved workflows, which connect Tomba to several systems and include approval steps, usually take longer. The free automation audit gives a realistic timeline for your specific setup.
Which plan or permissions do I need?
Generally, you need an active Tomba account that can issue an API key, and permission on your side to create and manage that key. The exact requirements depend on your Tomba plan and your internal access policies, so we confirm these during the audit before starting.