Grok LinkedIn Automation — Drive LinkedIn from Grok with MCP

What Grok can do through Linkydy

• Search leads in plain English — keyword/title text search with search_leads, or exact filters from a standard LinkedIn people-search URL with search_by_url.
• Build and manage a pipeline — matches are saved to the Linkydy CRM with name, title, company, and profile URL; Grok can list, review, and update them.
• Find work emails — call find_email for an approved profile URL; your Apollo.io API key must be set in Linkydy.
• Send personalized invites — connection requests with {FirstName}, {Company}, {JobTitle} fields, paced like a human.
• Warm up prospects — reactions and comments on your leads' posts before the invite lands.
• Export clean data — everything goes out via CSV export with emails, phones, and statuses.

How Grok connects

Grok supports bring-your-own MCP connectors: you register a server in the Grok web app and its tools become available in chat. Like ChatGPT — and unlike Claude Desktop or Cursor — Grok connects to MCP servers over the network rather than launching them on your machine. So the Linkydy server runs locally, with an HTTPS bridge in front of it.

Setup steps

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. Run the server locally (Node.js 18+ required):

   LINKYDY_TOKEN=PASTE_YOUR_TOKEN_HERE \
   npx -y linkydy-mcp

   This is the same server stdio clients configure as JSON:

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

4. Put an HTTPS bridge or tunnel in front of it and note the URL.
5. In the Grok web app, open the connectors settings, choose New Connector → Custom, and paste your server's URL. Grok discovers the Linkydy tools and lists them in your next chat. (Menu names shift between releases — if yours differ, look for MCP or connector settings.)
6. Toggle the MCP connection On in the Linkydy dashboard and keep Chrome open while Grok works.

Example prompts

Safety: what the extension enforces

Grok proposes; the extension disposes. Daily caps and human-like pacing apply to every connection request, reaction, and comment, and no prompt can raise them. There is no password sharing and no remote login — actions come from your own browser and IP, only while Chrome is open. Linkydy is deliberately not a 24/7 cloud bot; that constraint is what keeps your activity pattern human. LinkedIn itself caps invites at roughly 100–200 per week — see connection request limits.

MCP access requires Linkydy Premium; free accounts get an explicit premium_required response. For the broader risk picture, read Is LinkedIn automation safe? — and if you mostly prospect in Sales Navigator, the Sales Navigator MCP workflow shows the full search-to-outreach loop.