Cursor MCP for LinkedIn — Prospect Without Leaving Your Editor

If you're a founder or indie hacker, prospecting is the context switch that kills your afternoon: leave the editor, open LinkedIn, click through profiles, paste into a spreadsheet. With Linkydy's MCP server in Cursor, the same agent that just shipped your feature can also build the lead list for it — in the chat panel you already have open.

What you can do from Cursor

• Research leads mid-build — "find 20 CTOs at fintech startups in Berlin" while your tests run; results land in the Linkydy CRM, not your clipboard.
• Search with exact filters — apply company, location, industry, school, or other facets in standard LinkedIn people search, then give its URL to search_by_url.
• Find work emails — call find_email for an approved profile URL; your Apollo.io API key must be configured in Linkydy.
• Run supervised outreach — call get_safety_status, then send one approved request with {{FIRST_NAME}}, {{LAST_NAME}}, {{POSITION}}, and {{COMPANY}} placeholders.
• Close the loop — call get_campaign_stats for sent, accepted, pending, and acceptance rate; export the lead list manually from Linkydy when you need CSV.

Setup: .cursor/mcp.json

1. Install the Linkydy extension in Chrome and sign in with your email. Free credits, no card.
2. Open the Linkydy dashboard → AI Agent (MCP) → copy your pairing token.
3. Create .cursor/mcp.json in your project root (or ~/.cursor/mcp.json to enable it in every project):

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

4. Open Cursor Settings → MCP and confirm the linkydy server shows as enabled. (If your Cursor version files it elsewhere, look for the MCP or Tools section.)
5. Toggle the connection On in the Linkydy dashboard, keep Chrome open, and ask Cursor's agent for leads.

Requirements: Node.js 18+ on your PATH (npx ships with it), Chrome running with Linkydy signed in, and Premium for the private pairing token and On switch. The server relays actions to the extension over 127.0.0.1:8765; a closed browser means the tools cannot execute. The first npx run downloads the package.

Project-level config is handy for keeping the token out of shared dotfiles — add .cursor/mcp.json to .gitignore so your pairing token never lands in the repo. Use the global file for your own machine, the project file for a repo where only you run the agent.

Example prompts

Safety and pacing

The MCP bridge has no artificial daily cap. Tell Cursor to call get_safety_status, spread sends out, and ask before every write action. The extension auto-pauses if LinkedIn returns its own invite-limit or rate-limit signal. Nothing runs while Chrome is closed, and your LinkedIn password and cookies never leave your machine. See connection request limits and Is LinkedIn automation safe?.

MCP access requires Linkydy Premium; free accounts get an explicit premium_required response from the tools. Also using Claude Code in the terminal? The Claude setup guide covers claude mcp add with the same server.