Use LinkedIn with Claude — Linkydy MCP for Claude Desktop & Claude Code

What you can do with Claude + Linkydy

• Search LinkedIn from a prompt — keyword/title text search with search_leads, or exact filters from a standard LinkedIn people-search URL with search_by_url.
• Build lead lists hands-free — Claude saves matches straight into your Linkydy CRM with name, title, company, and profile URL.
• Find work emails — Claude calls find_email for an approved profile URL; your Apollo.io API key must be set in Linkydy.
• Send personalized invites — one connection request at a time with {{FIRST_NAME}}, {{LAST_NAME}}, {{POSITION}}, and {{COMPANY}} placeholders.
• Warm up prospects — reactions and comments on your leads' posts before the invite goes out.
• Review and export — ask Claude what's in the pipeline, then export everything to CSV.

Setup for Claude Desktop

1. Install the Linkydy extension and sign in with your email. Free credits, no card.
2. Open the Linkydy dashboard → AI Agent (MCP) → copy your pairing token.
3. Open Claude Desktop's config file (via Settings → Developer → Edit Config, or directly):
   • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
   • Windows: %APPDATA%\Claude\claude_desktop_config.json
4. Add the Linkydy server (merge into an existing mcpServers block if you have one):

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

5. Restart Claude Desktop. The Linkydy tools appear in the tools menu of a new chat.
6. Back in the Linkydy dashboard, toggle the MCP connection On.

Requirements: Node.js 18+ (npx ships with it), Chrome open with Linkydy signed in, and Premium for the pairing token and On switch. Keep the token private; regenerating it disconnects clients using the old value. If the paths above don't match your Claude version, open MCP settings and add the same command, args, and env by hand.

Setup for Claude Code

One command in your terminal:

claude mcp add linkydy \
  --env LINKYDY_TOKEN=PASTE_YOUR_TOKEN_HERE \
  -- npx -y linkydy-mcp

Verify with claude mcp list, or type /mcp inside a session to see the connection status. Then toggle the connection On in the Linkydy dashboard, keep Chrome open, and prompt away. Because Claude Code lives in your terminal, this pairs naturally with scripted workflows — for example, enriching a lead list right after your build finishes.

Use exact LinkedIn filters from Claude

For exact company, location, industry, school, past-company, or other facets, apply the filters yourself in LinkedIn's standard people-search UI and paste its address-bar URL. Claude then calls search_by_url. The current tool accepts linkedin.com/search/results/people/… URLs; it does not accept a Sales Navigator URL directly.

You: Use search_by_url with this filtered LinkedIn people-search URL:
     [paste URL]. Collect 20, then call list_leads.

Claude: ✓ 20 profiles collected
        ✓ Names, titles, companies, and locations ready to review

Example prompts

Safety and pacing

Claude never sees your LinkedIn password or session cookie, and actions run only through your own browser and IP. The MCP bridge has no artificial daily cap: ask Claude to call get_safety_status, spread sends out, and review each write action. The extension auto-pauses when LinkedIn returns its own invite-limit or rate-limit signal. If Chrome is closed or the Linkydy MCP switch is off, tools cannot execute.

MCP access is a Linkydy Premium feature; free accounts get an explicit premium_required response. For context on LinkedIn's own thresholds (≈100–200 invites per week), see connection request limits and Is LinkedIn automation safe?