How do I connect Evaboot to an AI assistant?

The Evaboot MCP server lets an AI assistant run Evaboot for you. You ask in plain language — “find HR directors at French SaaS companies and export the first 50 with emails” — and the assistant builds the search, launches the export, and polls it until the results are ready.

There is nothing to install. The server is hosted by Evaboot.

Server URL: https://mcp.evaboot.com/mcp

Before you start

• Your API key. It lives in the dashboard under Integrations → API. Clients that read a config file use this key. Claude and ChatGPT on the web sign in through your browser instead.
• A connected Sales Navigator account. Everything that touches LinkedIn — exports, searches, lead lists — runs on your own Sales Navigator seat. Email finding and email validation do not need one.

Treat the key like a password. It has full access to your Evaboot account, so never commit it to a repository or paste it into a shared document. Refresh issues a new key and immediately breaks anything still using the old one.

Connect your assistant

Claude Code

claude mcp add --transport http evaboot https://mcp.evaboot.com/mcp \
  --header "Authorization: Bearer YOUR_API_KEY"

Run /mcp to confirm. You should see Evaboot connected, with 37 tools.

Cursor

Create .cursor/mcp.json in your project:

{
  "mcpServers": {
    "evaboot": {
      "url": "https://mcp.evaboot.com/mcp",
      "headers": { "Authorization": "Bearer YOUR_API_KEY" }
    }
  }
}

VS Code (Copilot)

Create .vscode/mcp.json:

{
  "servers": {
    "evaboot": {
      "type": "http",
      "url": "https://mcp.evaboot.com/mcp",
      "headers": { "Authorization": "Bearer YOUR_API_KEY" }
    }
  }
}

Restart the client after editing either config file.

Claude on the web and desktop

Web chat interfaces cannot send a custom header, so they sign in through your browser instead of using the API key. Go to Customize → Connectors → Add custom connector, enter https://mcp.evaboot.com/mcp, then click Connect and authorize Evaboot. Leave the advanced OAuth fields empty — the server registers Claude automatically.

Connectors attach to your Claude account, so adding it once covers both web and desktop.

ChatGPT

Custom connectors need developer mode, under Settings → Apps → Advanced settings. Add the same URL as a custom connector and leave authentication set to OAuth. The connector then appears in the composer’s tool picker, where you enable it per conversation.

What you can do

The server exposes 37 tools. Your assistant picks the right ones; the list below is what it has to work with.

Building a search

Tool	What it does
build_search	Turns a description of an audience into a validated Sales Navigator URL. Resolves industries, titles, and company names against LinkedIn’s real filter catalog.
get_search_result	Polls a company-first search started by build_search.
build_search_url	Simpler single-shot URL builder. Free, capped at 100 calls per day.

Exporting leads

Tool	What it does
launch_export_from_url	Exports a Sales Navigator search or list URL. Asynchronous.
extract_profiles	Bulk export from 1 to 2500 profile URLs or ids. Asynchronous.
extract_single_profile	Extracts one profile and returns it immediately.
get_extraction, list_extractions	Fetch an export’s status and results, or list past exports.

Finding and validating emails

Tool	What it does
find_email_single, find_emails	Find one email immediately, or run a bulk job.
validate_email_single, validate_emails	Validate one address immediately, or run a bulk job.
get_email_finder_job, get_email_validation_job	Poll a bulk job.
list_email_finder_jobs, list_email_validation_jobs	List past jobs.

Your Sales Navigator lists and searches

Tool	What it does
list_lead_lists, list_account_lists	Read your existing lead and account lists.
create_lead_list, create_account_list	Create a new list on your seat.
add_leads_to_list, add_accounts_to_list	Add up to 999 entries per call.
create_lead_list_from_ids, create_account_list_from_ids	Create lists from profile or company ids, splitting at 999 per list.
delete_lead_list, delete_account_list	Delete a list.
search_leads, search_accounts	Run a raw search on your seat.
list_saved_searches, save_search, delete_saved_search	Manage your saved searches.
lead_list_from_search, account_list_from_search, get_sn_job	Paginate a search into a new list, then poll the job.
read_alerts	Read Sales Navigator alerts: job changes, posts, funding rounds.

Your account

Tool	What it does
get_quota	Remaining daily quota and credit balance.
verify_token	Confirms your API key is valid.

What the Sales Navigator tools change

Most of these tools only read. Some of them write, and they write to your real LinkedIn account rather than to anything inside Evaboot. It is worth knowing which is which before you let an assistant work unsupervised.

• Creating and deleting is real. create_lead_list, save_search, delete_lead_list, delete_account_list, and delete_saved_search all act on your own Sales Navigator seat. A list your assistant deletes is gone from LinkedIn, not just from Evaboot. Deleting a lead list removes the list itself; the leads inside it stay in your LinkedIn account.
• Some searches write lists as a side effect. When you name an industry or a vertical, build_search may run a company-first search, which creates account lists on your seat while it works. lead_list_from_search and account_list_from_search do the same by design, saving up to 1000 leads into a new list.
• Long jobs should not be retried. Search-to-list jobs run for several minutes. Starting one again because it looks slow re-runs the writes and leaves you with duplicate lists. Poll get_sn_job instead.
• Reading lists returns a lot of data. The list tools return LinkedIn’s raw response, including image URLs and internal identifiers. An assistant reading a large account will work through a lot of text to answer a small question.

If you would rather keep the assistant read-only, say so in your instructions to it, or use a client that asks for approval before each tool call.

Credits and quota

Credits and daily quota are two separate limits, and running out of one does not affect the other.

• Credits come from your Evaboot balance. Exports cost 1 credit per lead, email finding costs 1 per prospect, and validation costs 0.5 per address. For exports the balance is checked when the job launches and charged when it completes, based on the leads actually found.
• Daily quota is tied to your connected Sales Navigator seat and resets each day. Ask your assistant to check get_quota before a large run.
• Email finding and validation need no Sales Navigator seat. They draw on credits only, so they keep working even when your quota is 0 or your LinkedIn connection has dropped.

If it didn’t work

The client reports 401, or the connection fails. On the API-key path, check the header is exactly Authorization: Bearer <key> and that the key is the current one. On the browser sign-in path, disconnect and reconnect to redo the consent screen.

Exports fail with 429, or list tools fail with 409. Both mean the same thing: Evaboot has lost its connection to your LinkedIn account. The two messages are worded differently, and neither gives the full fix.

What you see	What it means
429 — No connected LinkedIn account.	Returned by the export tools.
409 — Your LinkedIn connection has expired or was revoked.	Returned by the list and search tools.

Opening Sales Navigator is not enough to reconnect. Run one extraction from the Evaboot Chrome extension. That is what re-links the seat. Your assistant can confirm it worked by calling get_quota and checking that has_valid_salesnav is now true.

get_quota shows credits but 0 quota. Your LinkedIn connection has dropped. Credits are unaffected, which is why email tools still work. Reconnect with an extraction as above.

A raw Sales Navigator search returns nothing, with no error. search_leads and search_accounts take a rest.li query, not the query= value copied out of a Sales Navigator URL. A copied value is already encoded once, gets encoded again, and LinkedIn answers with zero results rather than an error. Build the search with build_search instead.

The assistant shows no tools after connecting. Refresh the connector’s tool list, or remove the server and add it again.

Related articles

• How Does the Evaboot API Work?
• What Is Evaboot Integration and How Does It Work?
• How Does the Sales Navigator Export Work?