Skip to main content

How to connect Tomba to Cursor, Windsurf, and VS Code

Connect Tomba to Cursor, Windsurf or VS Code so you can ask your AI assistant to find and verify emails.

Written by Tomba.io Team

Connect Tomba to the AI assistant in your code editor, then ask it to find and verify emails in plain language. The setup takes one web address, and there's nothing to install.

You connect through Tomba's remote MCP server. MCP is a standard way for AI assistants to use other tools. Tomba hosts the server, so it runs online and not on your computer.

Before you start

You need a Tomba account. How you connect depends on your editor:

Editor

Where to add Tomba

How you connect

Cursor

Its MCP settings file. Connect a client shows where it is

API key and secret

Windsurf

Open MCP config file, in the … menu of the Cascade panel

Sign in, or API key and secret

VS Code

MCP: Open User Configuration, in the Command Palette

Sign in, or API key and secret

An API key and secret are private codes that let your editor use your Tomba account.

Windsurf is now called Devin Desktop. The setting in the table is for its Cascade assistant. Its Devin Local assistant, the default for new tabs, uses different settings.

Connect your editor

Step 1. Open Integrations and find the MCP group. Select Connect on the Remote MCP Server card to open the setup guide.

The MCP group on the Integrations page, with the Local MCP Server, Remote MCP Server and Composio names outlined

Step 2. If your editor uses an API key and secret, copy them from API Keys. Skip this step if you'll sign in.

The API Keys page with an arrow on the API Key & Secret column, where each blurred value has a show and a copy button

Step 3. Open the setting for your editor, as shown in the table above.

Step 4. Add a server with the address https://mcp.tomba.io/mcp. You can copy the exact text for your editor from Connect a client in the Tomba docs.

Step 5. If your editor asks, sign in to Tomba in the window that opens and approve access.

Your editor now shows Tomba as connected. Where it lists Tomba's tools, it shows 28.

⚠️ Important: Your key and secret are private. Don't share a file that contains them.

Ask your assistant

Tell it what you want in plain language, such as:

The assistant picks the right Tomba tool for you.

💳 Credits: Each search is charged as if you ran the same search in Tomba. For example, finding an email uses 1 search credit when an email is found, and verifying one uses 1 verification credit.

Common questions

Can I run the server on my own computer instead?

Yes, but it takes more setup. See How to set up the Tomba local MCP server. The hosted server is easier, and it has the same 28 tools.

Why does Tomba show as connected, but every search fails?

Your key or secret is probably wrong, or your key has expired. Tomba only checks them when the assistant runs its first search. Copy both again from API Keys.

How do I remove access?

If you signed in, remove the app in Settings > Connected Apps. If you used a key and secret, reset your key on API Keys.

For developers: see the Tomba docs.

Related articles

Did this answer your question?