Tomba MCP server
Tomba finds and verifies professional email addresses for B2B sales and outreach, used by sales teams building prospect lists. Connect through Arc0 to use the actions your identity is allowed to call.
Agent workflows for Tomba.
Find email
Use when finding work email by name and domain; not for webmail or bulk sweeps. Costs 1 search credit when an email is returned with verification status other than unknown. Null means no match. Timeouts may still be charged.
Find author
Use when finding the email of one article author; not for multi-author pages or bulk harvesting. Costs 1 search credit when an address is returned. Null means no match. Timeouts may still be charged.
Find linkedin
Use when finding work email for one exact LinkedIn person profile; not company pages or bulk harvesting. Costs 1 search credit when an address is returned. Null means no match. Timeouts may still be charged.
7 Tomba actions, graded by risk.
These actions come from the Arc0 registry. Your identity, provider permissions and Arc0 policies determine which actions can run.
read
7Look things up, subject to your permissions.
- tomba.find_emailFind email
Use when finding work email by name and domain; not for webmail or bulk sweeps. Costs 1 search credit when an email is returned with verification status other than unknown. Null means no match. Timeouts may still be charged.
- tomba.find_authorFind author
Use when finding the email of one article author; not for multi-author pages or bulk harvesting. Costs 1 search credit when an address is returned. Null means no match. Timeouts may still be charged.
- tomba.find_linkedinFind linkedin
Use when finding work email for one exact LinkedIn person profile; not company pages or bulk harvesting. Costs 1 search credit when an address is returned. Null means no match. Timeouts may still be charged.
- tomba.search_domainSearch domain
Use when reading a bounded company email page; not for broad sweeps or enumeration. Costs 1 search credit per page with results (limit <=10). Webmail returns no emails. Timeouts may still be charged.
- tomba.verify_emailVerify email
Use when checking one exact email; not for bulk verification or finding an address. Costs 1 verification credit per result, except disposable/unknown are free. Timeouts may still be charged.
- tomba.get_accountGet account
Use when inspecting account allowances; not daily history. Free (0 credits). available is allowance; remaining = available - used. For workspace members, used covers only their own usage, not the shared balance.
- tomba.get_usageGet usage
Use when reading your daily credit usage; not team totals or remaining balance. Free (0 credits). Duration includes today; days without charges have no row.
write
0Create and change things. Allow, or ask the user first.
- No write actions.
destructive
0Delete, cancel or archive. Ask first, or deny outright.
- No destructive actions.
Control access to Tomba.
Connect the intended Tomba account, authorize your AI client and set policies for its tools.
Provider permissions and Arc0 policy both apply. Allow reads, require approval for selected writes, or deny destructive actions. The audit log records execution decisions.
Configure policies and approvalsExample policy choices
- Read actions: allow where authorized
Arc0 MCP endpoint: https://api.arc0.ai/mcp
How Tomba connects.
Connect Tomba using API key and API secret. OAuth grants the provider scopes shown during consent; API keys and other credentials retain the permissions configured at the provider. Arc0 stores credentials in its encrypted vault and does not pass them to the model. Disconnect to remove access through Arc0; revoke a key at the provider to invalidate it there. Token refresh and provider-side revocation depend on the authentication lane and provider.
The connection serves authorized calls through Arc0 MCP and REST. How Arc0 handles credentials →
- AUTH
- API key and API secret
- CREDENTIALS
- Per-tenant encrypted vault
- MODEL SEES
- Results only, never credentials
- AUDIT LOG
- Every call, on every plan
Use Tomba with your AI client.
Sign in to Arc0 and connect Tomba in My apps. Then authorize your AI client separately. It only receives tools and accounts allowed for that identity.
Tomba with Claude
Claude Desktop + Claude Code
- In Claude Desktop, add Arc0 through the remote MCP settings and use OAuth. Follow the generic remote-client steps if your account’s interface differs.
- For Claude Code, run the command below. Open /mcp, select Arc0, and authenticate in your browser. Select your workspace and review access.
- Check the connection with claude mcp get arc0.
claude mcp add --transport http --scope user arc0 https://api.arc0.ai/mcpFull MCP setup and troubleshootingTomba with ChatGPT
ChatGPT on the web
- Open Plugins in ChatGPT, select the plus button, then Add custom MCP server.
- Name it Arc0, enter the server URL below, and choose OAuth. Use dynamic client registration if asked; no Arc0 API key is needed.
- Review the notice and select Create as a plugin. Complete Arc0 sign-in, workspace selection and consent, then install and select the plugin in your conversation. Labels and access vary by account; managed workspaces may require administrator approval.
https://api.arc0.ai/mcpFull MCP setup and troubleshootingTomba with OpenAI Codex
Codex app + CLI
- Run the registration command below. The app and CLI share ~/.codex/config.toml.
- Complete browser OAuth, choose your Arc0 workspace, and review access. If authentication does not start, run codex mcp login arc0.
- Check codex mcp list, then open a new Codex chat. Inspect an existing arc0 entry before changing it.
codex mcp add arc0 --url https://api.arc0.ai/mcpFull MCP setup and troubleshootingTomba with Cursor
Remote MCP setup
- Add Arc0 in your client’s remote MCP settings using the server URL below.
- Choose OAuth, sign in to Arc0, select the intended workspace and review access.
- Confirm the server is connected and start with an allowed read. These are generic remote-MCP steps; consult your client’s settings for its current interface.
https://api.arc0.ai/mcpFull MCP setup and troubleshootingTomba with VS Code
Remote MCP setup
- Add a remote HTTP MCP server named Arc0 using the URL below.
- Use OAuth and finish Arc0 sign-in, workspace selection and consent.
- Confirm discovery succeeds before requesting a read. These are generic remote-MCP steps; client UI and availability may differ.
https://api.arc0.ai/mcpFull MCP setup and troubleshootingTomba with Any MCP client
Streamable HTTP
- Use a client that supports remote MCP over Streamable HTTP. Add the server URL below and choose OAuth.
- For a client without OAuth, use a self-bound API key with execute permission in the X-API-Key header. Store it in secret storage or an environment variable, outside source control. Never send both an API key and an OAuth bearer token.
- Use the MCP clients guide for the SDK transport example and Embedded identity for business-managed end users.
https://api.arc0.ai/mcpFull MCP setup and troubleshootingAfter setup, ask your agent to find an allowed read action, load its schema, and execute it on the intended account. Check Activity for the receipt. A connected MCP client alone does not confirm a successful provider call.
Tomba and Arc0, answered.
Does Tomba work with Claude Desktop and Claude Code?
Yes, after connecting the account and authorizing the client. Use Arc0’s remote MCP endpoint with OAuth. Claude Code has a documented registration command; Desktop uses the generic remote-client setup.
Can I use Tomba with OpenAI Codex, ChatGPT and Cursor?
Yes, after connecting the account and authorizing the client. Codex and ChatGPT have setup instructions in Arc0’s MCP clients guide. Cursor uses the generic remote-MCP steps. Tool access remains scoped to the authorized identity.
Is this the official Tomba MCP server?
This is Arc0’s integration page, not a claim of an official Tomba server. Arc0 adds a shared connection, policy and audit experience across apps. Consult Tomba for its own current MCP offerings.
Which Tomba actions are supported?
7 registry-defined actions: 7 read, 0 write and 0 destructive. Provider permissions, access enablement and Arc0 policy determine what can execute.
Which permissions does Tomba need?
Connect Tomba using API key and API secret. OAuth grants the provider scopes shown during consent; API keys and other credentials retain the permissions configured at the provider. Arc0 stores credentials in its encrypted vault and does not pass them to the model. Disconnect to remove access through Arc0; revoke a key at the provider to invalidate it there. Token refresh and provider-side revocation depend on the authentication lane and provider.
Can I restrict writes in Tomba?
You can deny write and destructive actions or require approval. Provider scopes and Arc0 action policies are separate controls; a policy does not grant additional provider permissions.
What does Tomba through Arc0 cost?
See Arc0 pricing for current connectivity plans. The provider may require its own subscription or charge per request. Arc0 plan allowances do not make third-party data or paid actions free.
Plug Tomba into your agent.
Tomba MCP server: 7 actions including find email, find author, find linkedin. Connect through Arc0.
Free to build · MCP + REST · Audit log on every plan
Tomba and its logo are trademarks of their respective owners. Arc0 is not affiliated with or endorsed by Tomba.