Build Sales Navigator searches, export leads, and find or verify professional emails through a hosted MCP endpoint.
Copy the AI prompt to install this server into Claude Code, Cursor, or another agent β or use 1-click editor setup below.
π‘ Paste the JSON block into your client's configuration file under mcpServers, then restart the application.
Inspect callable tools, capabilities, and parameters exposed to AI agents by Evaboot.
build_sn_search_from_promptTurn a natural-language audience into a Sales Navigator search URL.
get_account_based_search_jobPoll an account-based lead search started by `build_sn_search_from_prompt`.
search_sn_leadsRead one page of a Sales Navigator lead search.
search_sn_accountsRead one page of a Sales Navigator account search.
list_saved_searchesList your saved Sales Navigator searches.
save_searchSave a Sales Navigator search on your seat.
Evaboot MCP server exposes Evabootβs hosted service through MCP. It works with LinkedIn Sales Navigator to build searches from natural-language audience descriptions, read lead or account results, manage saved searches and lists, read alerts, and export profiles or search results.
The service also supports professional email workflows. Agents can find an email for one person or for a batch, verify one or many addresses, and retrieve the status and results of asynchronous jobs. Sales Navigator exports and email jobs can be checked, listed, or cancelled where the relevant operation supports it.
The remote MCP endpoint is available at https://mcp.evaboot.com/mcp using Streamable HTTP. An MCP client sends tool calls to the hosted service rather than running a local Evaboot process. Long-running searches, exports, list creation tasks, email-finder jobs, and verification jobs expose separate status or result tools for polling.
A typical workflow starts with build_sn_search_from_prompt, followed by a lead or account search or an export. The resulting records can be placed in Sales Navigator lists, passed to email-finding or verification tools, or pushed to a connected destination. The available tools also cover recurring exports, integration targets, and write-back status.
Evaboot MCP server requires an Evaboot account and a LinkedIn account with Sales Navigator connected through the Evaboot Chrome extension. No local installation is required because the server is hosted by Evaboot.
Clients that support OAuth can use OAuth 2.1 with PKCE and dynamic client registration. Add the remote URL, sign in through the browser, and approve access. Clients without OAuth support can send an Evaboot API key as a bearer token; the key is available from the API page of the Evaboot dashboard.
The repository documents connections for Claude, Cursor, and VS Code. Evaboot also provides authentication endpoints for authorization, token exchange, and client registration.
The documented tool groups cover:
The LinkedIn and Sales Navigator connection is a prerequisite for Sales Navigator operations. Export availability is subject to the accountβs remaining daily quota and credit balance. Some operations are asynchronous, so callers need to poll the corresponding job or export status tool before using results.
The documentation repository is MIT-licensed, while the Evaboot hosted service is proprietary. Evaboot MCP server is therefore a hosted service rather than a self-contained server package to install and run locally.
Factual signals from GitHub, npm, and our automated checks β not a rating.
No reviews yet β be the first to share how this listing worked for you.
Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.
[](https://allmcps.com/mcp/evaboot-2)<a href="https://allmcps.com/mcp/evaboot-2"><img src="https://allmcps.com/api/badge/evaboot-2?style=directory" alt="Evaboot on AllMCPs" /></a>