HomeGuides › Sales Navigator AI

Sales Navigator + AI: collect first, then hand off to MCP

Use Sales Navigator's filters and Linkydy's in-page collector to build the right list, then hand those saved leads to Claude, ChatGPT, Cursor, or another MCP client for review, work-email lookup, and supervised outreach.

The current Linkydy MCP server does not accept Sales Navigator URLs or translate a prompt into Sales Navigator facets. The reliable workflow is hybrid: you choose precise filters in Sales Navigator, Linkydy collects the results into its CRM, and the agent works with that saved list.

Product boundary: search_by_url accepts standard linkedin.com/search/results/people/… URLs only. For Sales Navigator, collect with the extension first, then call list_leads.

Four things AI changes in a Sales Navigator workflow

1. You keep control of exact Sales Navigator filters

Choose title, geography, industry, headcount, school, past company, and other facets in Sales Navigator itself. This is more reliable than asking a model to guess LinkedIn's internal filter IDs. If you prefer prompt-driven search, use standard LinkedIn people search: apply exact filters there and pass its URL to search_by_url.

2. The extension creates the handoff

Collect the filtered Sales Navigator results with Linkydy. The same local lead storage is available to list_leads, so the agent can immediately review names, titles, companies, locations, profile URLs, and statuses. For work-email lookup, find_email takes one profile URL and requires your Apollo.io API key.

3. First lines written from context

Template fields like {FirstName}, {Company}, and {JobTitle} keep messages personalized at the mail-merge level; an AI agent goes further and drafts opening lines per prospect from what it knows about their role and company. You approve the angle once, and the agent applies it lead by lead.

4. Campaign status stays visible

The agent can call get_campaign_stats for sent, accepted, pending, and acceptance rate, and get_safety_status for today's invite count. The current MCP toolset sends connection requests but does not expose a general follow-up-message scheduler.

How it works under the hood

Linkydy ships its own MCP (Model Context Protocol) server. The implemented toolset is: get_account, search_leads, search_by_url, list_leads, find_email, send_connection, react_to_posts, comment_on_post, get_campaign_stats, and get_safety_status. Actions execute through the extension in your own browser session.

The safety model: your LinkedIn password and session cookie stay in Chrome. The MCP bridge has no artificial daily cap, so the agent must use get_safety_status and pace sends. The extension auto-pauses if LinkedIn returns its own invite-limit or rate-limit signal. Why the browser architecture matters is covered in Is LinkedIn automation safe?.

Set it up in four steps

Works with Claude Desktop and Claude Code, ChatGPT, Grok, Cursor — any MCP-compatible client. Client-specific walkthroughs live at Linkydy + Claude, Linkydy + ChatGPT, and the main MCP setup page.

Install & sign in

Install Node.js 18+, add Linkydy to Chrome, and sign in. Premium unlocks the private pairing token and On switch; free users can still read the setup guide.

Copy your pairing token

Open Linkydy dashboard → AI Agent (MCP) → copy the pairing token. Keep it out of repositories; regenerating it disconnects clients using the old token.

Add the server to your client

Paste the config below into your MCP client's configuration, with your token in place of the placeholder.

{
  "mcpServers": {
    "linkydy": {
      "command": "npx",
      "args": ["-y", "linkydy-mcp"],
      "env": { "LINKYDY_TOKEN": "PASTE_YOUR_TOKEN_HERE" }
    }
  }
}

Step four: back in the dashboard, toggle the MCP connection On. Keep your browser open while the agent works — Linkydy runs in your session, not in a cloud. That's the whole setup; the MCP page has troubleshooting notes per client.

Prompts to try on day one

  • "I collected the Sales Navigator results in Linkydy. Call list_leads with filter ‘fintech’ and show names, titles, companies, locations, and profile URLs."
  • "For this approved profile URL, call find_email. If it says not_configured, remind me to add my Apollo.io API key in Linkydy."
  • "Use search_by_url with this standard LinkedIn people-search URL: [paste URL]. Collect 15 profiles, then call list_leads."
  • "React to the two most recent posts from this approved profile. Draft any comment first and wait for approval."
  • "Call get_safety_status, show today's invite count, and wait for my approval before one send_connection call."

Notice what these have in common: every prompt maps to an implemented tool and includes a review point. When you want raw data, export it manually from Linkydy using CSV export; CSV export is not currently an MCP tool.

Honest limits

  • Your browser must be open. The agent orchestrates, but the extension executes in your live session. No browser, no actions — that constraint is also the safety feature.
  • No artificial MCP cap. The agent should call get_safety_status, pace sends, and stop when LinkedIn signals its own limit; the extension auto-pauses on invite-limit and rate-limit responses.
  • Premium feature. Lead collection and enrichment start free, but driving Linkydy from an AI agent requires a Premium plan.
  • Review beats autopilot. The best results come from agent-drafted, human-approved outreach — approve the angle and the list, then let the pacing do its work.

FAQ

Does Sales Navigator have built-in AI?

Sales Navigator includes some native AI assistance, like account and lead summaries, but it cannot run your workflow — it will not build lists from a plain-English brief, find emails, or send paced outreach for you. That orchestration layer is what an external AI agent connected through MCP adds.

What is MCP and why does it matter for prospecting?

MCP lets AI clients call Linkydy's implemented tools. The current server can search standard LinkedIn people pages, list saved leads, find a work email with your Apollo key, send one connection request, react, comment, and report safety or campaign status. It does not accept Sales Navigator URLs directly.

Do I need Sales Navigator to use Linkydy's AI agent?

No. The MCP search tools work with standard LinkedIn people search. Sales Navigator is optional: use its sharper filters manually, collect the results with the Linkydy extension, then let the agent work with the saved Linkydy lead list.

Is it safe to let an AI agent send connection requests?

Any automation carries risk. The MCP bridge has no artificial daily cap, so the agent should call get_safety_status, pace sends, and ask before write actions. Linkydy auto-pauses if LinkedIn returns its own invite-limit or rate-limit signal.

Which AI clients work with Linkydy?

Any MCP-compatible client: Claude Desktop and Claude Code, ChatGPT, Grok, Cursor, and others. Setup is the same everywhere — install the extension, copy your pairing token from the dashboard, add the Linkydy MCP server to the client config, and toggle the connection on. The AI agent is a Premium feature; free accounts get a clear premium_required response.

Turn a filtered Sales Navigator list into an agent workflow

Collect the right profiles with Linkydy, then connect Claude, ChatGPT, Grok, Cursor, or another MCP client for supervised review, email lookup, and outreach.

Free credits included · No credit card required