The current Linkydy MCP server does not drive Sales Navigator search directly. Its URL tool only accepts standard linkedin.com/search/results/people/… pages. The useful workflow is a clean handoff: collect from Sales Navigator with the Chrome extension, then let your agent work with the same saved Linkydy lead list.
The accurate workflow
Filter in Sales Navigator
Use your own Sales Navigator seat to choose job title, company, geography, industry, past role, school, and other facets. Linkydy never proxies or resells your subscription.
Collect with the extension
Save matching profiles from the Sales Navigator page into the Linkydy CRM. Names, titles, companies, profile URLs, and statuses share the same local lead storage the MCP tools read.
Hand off to the agent
Ask the agent to call list_leads, review the saved segment, optionally call find_email per approved profile, then draft or send one supervised connection request at a time.
Connect your MCP client
- Install Node.js 18+ and Linkydy. Sign in to LinkedIn and Sales Navigator in the same Chrome profile.
- Open Linkydy dashboard → AI Agent (MCP) → copy the private pairing token. Premium unlocks the token and On switch.
- Add the local server to your MCP client:
{ "mcpServers": { "linkydy": { "command": "npx", "args": ["-y", "linkydy-mcp"], "env": { "LINKYDY_TOKEN": "PASTE_YOUR_TOKEN_HERE" } } } } - Toggle Linkydy's MCP connection On. The server listens on 127.0.0.1:8765 for the extension. Client-specific guides: Claude · ChatGPT · Grok · Cursor.
Prompt after collecting Sales Navigator leads
I already collected the approved Sales Navigator results in Linkydy. 1. Call get_account and confirm the connection. 2. Call list_leads with filter: "Nordics e-commerce" and show me the names, titles, companies, locations, and profile URLs. 3. Wait for my approval before any write action. 4. For one approved profile at a time, call find_email if my Apollo.io key is configured, or draft a connection request under 200 characters. 5. Call get_safety_status before send_connection and pace sends. 6. Finish with get_campaign_stats.
Prompt examples that match the real tools
Safety model, accurately stated
- Your seat, your session — collection and MCP actions run in your own Chrome profile. No password or cookie export.
- No artificial MCP cap — use get_safety_status to report today's invite count and pace sends instead of bursting.
- LinkedIn-triggered auto-pause — the extension stops when LinkedIn returns its own invite-limit or rate-limit signal.
- Apollo key for email — find_email needs your own Apollo.io API key configured in Linkydy.
- Browser-open requirement — Chrome and the Linkydy MCP switch must remain on for actions to execute.
Linkydy