LinkedIn MCP server

LinkedIn MCP for Claude, ChatGPT, Cursor and Grok Bot

Turn LinkedIn engagement into qualified conversations from Claude, ChatGPT, Cursor or Grok Bot.

Let your AI agent post, comment, DM and run lead magnets on LinkedIn through LeadShark’s Apex MCP, inside the same limits, pacing and approvals as the rest of your account.

Apex is LeadShark’s LinkedIn MCP server. LinkedIn doesn’t publish an official MCP server for personal profiles, so every LinkedIn MCP is third-party.

7-day free trial, no card. See plans.

Apex MCP server URL

https://apex.leadshark.io/mcp

Connect Claude.ai, ChatGPT, Grok or Grok Bot to this URL and sign in on apex.leadshark.io. Cursor, Claude Code, Codex, OpenClaw and Hermes Agent connect to the same hosted server. See the setup steps below. Full MCP docs.

Connect in minutes

Connect your assistant to the hosted server and sign in on apex.leadshark.io. No local LeadShark package or API key is needed. Full instructions are in the setup guide.

Fastest way: paste this into your agent

If your agent can read a URL, paste:

set up LeadShark: https://apex.leadshark.io/mcp/setup.txt

The guide explains how to connect. Follow your assistant's steps and approve access on apex.leadshark.io.

Claude.ai

About a minute · OAuth, no install

  1. Open Customize, then Connectors, click + and choose Add custom connector.
  2. Name it “LeadShark Apex” and paste https://apex.leadshark.io/mcp. Leave the optional OAuth fields blank.
  3. Click Connect, sign in to LeadShark, review mcp:read and mcp:write, and Approve.
  4. In Configure, set read-only tools to Always allow. Leave write tools on Ask every time.

ChatGPT

A couple of minutes · OAuth, no install

  1. Open Settings, then Apps, turn on Developer mode under Advanced, then click Create app.
  2. Set Connection to Server URL and paste https://apex.leadshark.io/mcp. Set Authentication to OAuth.
  3. Click Sign in with LeadShark Apex, review the scopes and Approve.

Grok

Hosted server with sign in

  1. Open https://grok.com/connectors.
  2. Click New Connector, then choose Custom.
  3. Paste https://apex.leadshark.io/mcp as the server URL.
  4. Sign in on apex.leadshark.io and approve access.

The account needs Pro+ or Apex. On any other plan the server refuses tool calls.

Grok Bot

Add a custom server in chat

  1. Ask: "Add a custom MCP server called LeadShark at https://apex.leadshark.io/mcp".
  2. Confirm with "Add it".
  3. Click Authorize on the connect card.
  4. Sign in on apex.leadshark.io and approve access.

Use the words "custom MCP server" so Grok Bot adds your server instead of looking for a catalog plugin.

The account needs Pro+ or Apex. On any other plan the server refuses tool calls.

Cursor, Claude Code and Codex

Hosted server with sign in

  1. In Cursor, add the URL configuration below to .cursor/mcp.json. Open Cursor Settings, then MCP, click Connect next to leadshark and sign in on apex.leadshark.io.
  2. In Claude Code, run the command below. Then run /mcp, select leadshark and sign in on apex.leadshark.io.
  3. In Codex, run the command below and sign in when the browser opens. If it does not open, run codex mcp login leadshark. Check the connection with codex mcp list.

The account needs Pro+ or Apex. On any other plan the server refuses tool calls.

OpenClaw and Hermes Agent

Hosted server with sign in

  1. In OpenClaw, save the server with the command below. Run openclaw gateway stop, then openclaw mcp login leadshark, open the printed link and sign in on apex.leadshark.io. Start the Gateway again with openclaw gateway start.
  2. In Hermes Agent, add the server to ~/.hermes/config.yaml as below. Run hermes mcp login leadshark and sign in on apex.leadshark.io, then /reload-mcp or start a new session.
  3. On a server with no browser, finish sign in with the code login OpenClaw prints, or hermes mcp login leadshark --flow device.

Then ask from Telegram, WhatsApp, Slack or Discord, wherever your agent lives.

The account needs Pro+ or Apex. On any other plan the server refuses tool calls.

Cursor: .cursor/mcp.json

{
  "mcpServers": {
    "leadshark": {
      "url": "https://apex.leadshark.io/mcp"
    }
  }
}

Hermes Agent: ~/.hermes/config.yaml

mcp_servers:
  leadshark:
    url: "https://apex.leadshark.io/mcp"
    auth: oauth

Claude Code

claude mcp add --transport http leadshark https://apex.leadshark.io/mcp

Codex

codex mcp add leadshark --url https://apex.leadshark.io/mcp

OpenClaw

openclaw mcp set leadshark '{"url":"https://apex.leadshark.io/mcp","transport":"streamable-http","auth":"oauth"}'

Apex MCP, as seen on mcpexplorer.com

How LinkedIn MCP servers connect to LinkedIn

LinkedIn doesn’t publish an MCP server for acting from your personal profile, so every LinkedIn MCP is built by a third party. What separates them is the route into your account. That route decides what the agent can do, and what holds it back when it tries to do too much.

LinkedIn MCP connector types: how each reaches LinkedIn, what it can do and what stops it
Connector typeHow it reaches LinkedInWhat it can doWhat stops it
Browser or cookie scraperSigns in as you with a copied session cookie or an automated browser, often running on your own machine.Reads profiles and the feed. Some versions also send DMs and connection requests.Usually nothing beyond what its author coded. Actions fire as fast as the agent thinks, with no shared caps, pacing or audit log.
Data extraction serviceHands your agent profile and company data that a third party has already collected.Looks up people and companies for your agent to read.It can’t comment, connect or DM, so there is nothing to govern, and nothing that turns a lookup into a conversation.
Content-only MCPPublishes through LinkedIn’s official API after you approve it with OAuth.Drafts, schedules and reports on your own posts. No DMs and no connection requests.The API scope itself. It can’t read who commented or message anyone, so engagement stays on the post.
Generic automation connectorGoes through a workflow tool’s built-in LinkedIn integration.A few basic actions, such as sharing a post.Whatever steps you wire up yourself. No LinkedIn-specific limits, pacing or approvals.
LeadShark ApexRuns in the cloud on your own LinkedIn account after a one-time connect with our extension. LeadShark never asks for your LinkedIn email or password.51 tools: search people and posts, read who engaged, enrich, comment, connect, DM, schedule posts and run comment-to-DM automations.Caps shared with your automations, human pacing, off-hours, approve-first mode, Emergency Stop and a full audit log. The agent can’t raise its own limits.

See, decide, act

Apex MCP exposes 51 tools. They follow a simple loop, plus the automation and scheduling tools LeadShark was built on. Pro+ is the MCP baseline; tools that read or act on other people are Apex.

See

Search people and posts, read who engaged, pull a person’s recent activity, and surface your hottest inbound leads.

Decide

Enrich a profile, check your shared history, judge ICP fit, and read the agent’s own action log before anything is sent.

Act

Comment, react, connect, DM or InMail, schedule a post, and run the comment-to-DM automations LeadShark was built on.

Pro+ and Apex

Search people, companies and posts

Find ICP-fit people or companies (Pro+), and posts by keyword (Apex), then act on what you find.

Pro+ and Apex

Turn engagement into a lead list

Read a post’s commenters and reactors (Pro+), or a person’s recent comments and reactions (Apex).

Pro+

Enrich before you reach out

Turn a person or company into a structured profile. Work-email lookup is Apex.

Apex

Act as yourself on LinkedIn

Comment, react, reply to a comment, and send a DM, or an InMail with your own credits. Connection requests are on Pro+ and Apex.

Pro+

Run lead-magnet automations

Create and edit comment-to-DM automations, build lead pages, and schedule posts with the automation attached.

Apex

Stay inside the budget you set

Check remaining limits, pause or tighten a channel, and read every governed action: sent, refused or waiting.

Prompts to try

Ask it in plain language. Copy a prompt, paste it into Claude, ChatGPT or Cursor with Apex MCP connected, and swap in your own post or person.

Find leads

Who engaged with my last post? Build me a lead list, warmest first.

Research a person

What has Jane Doe been commenting on lately? Draft a connection note and check we haven’t talked before.

Comment-to-DM automation

Automate my latest post: reply to anyone who comments “guide” and send them the link by DM.

Schedule a post

Schedule my guide post for Tuesday 9am and DM anyone who comments “guide”.

Check limits

How many DMs and connection requests do I have left today? If I’m close, set my daily DM limit to zero.

Audit log

What have you already done today? Anything refused or waiting for approval?

Safer than ungated LinkedIn automation

An agent with unlimited LinkedIn access will fire actions as fast as it can think. Apex paces every action like a person would, inside your daily limit of 0 to 250 DMs a day (150 recommended max). The question to ask any LinkedIn MCP server is not “what can it do?” but “what stops it?”

Your limits, shared with automations

DMs, comment replies and daily/weekly connection requests all draw from the same caps you set in the dashboard. The agent cannot route around them.

The agent cannot raise its own budget

It can check what’s left, lower a cap or pause a channel immediately. Raising a cap is staged for you to approve.

Human pacing and off-hours

Every write is velocity-paced and honors a shared cooldown. With off-hours on, DMs, comments, reactions and connection requests wait between 10 PM and 6 AM in your timezone. Reads still work.

Approve-first when you want it

Put the account in queue mode and every write waits for your review. In Claude, leave write tools on “Ask every time” so it checks with you before each comment, connection or message.

Emergency Stop and do-not-engage

One switch under Agent, then Logs blocks every agent write instantly: automations, MCP, everything. Archive a lead and DMs to them are refused at the send step.

A full audit log

Every governed action is logged. Your agent can read what it did, what was refused and why, and what’s pending, and you see the same trail in the dashboard.

Daily DMs stay inside a limit you set, anywhere from 0 to 250 a day (we recommend a maximum of 150). None of this makes LinkedIn automation risk-free. It does mean the agent operates inside rules you set, at a pace that looks like a person, with a record of everything.

2.8M

Total DMs delivered

3.1M+

Comments processed

<10m

Average response time

2.8M+ DMs and 3.1M+ comments across 1,500+ creators, with an average response time under 10 minutes. Same platform the MCP writes through.

Pro+ connects the MCP. Apex is the full agent.

Pro+ is the MCP baseline: automations, scheduling, lead pages, people and company search, post engagers, connection requests, invitation triage, discovery and enrichment. Apex adds post search, activity, inbox, signals, and acting as yourself. New accounts get a 7-day free trial with no card. Any account not already on Apex can unlock a one-time 72-hour Apex window in Settings.

Guides for Claude, ChatGPT and agents on LinkedIn

Setup, limits and safety, in more depth.

LinkedIn MCP questions

Longer answers live in the setup guide. Something else? Talk to us.

Does LinkedIn have an official MCP server?

Not for acting from your personal profile. As of October 2026, every LinkedIn MCP server is built by a third party, so compare them on how they protect your account: limits, pacing, approvals and logging. Apex MCP is LeadShark's, at https://apex.leadshark.io/mcp. For the official API and what it gates, see LinkedIn API: what you can build.

Is there a LinkedIn MCP for Claude?

Yes. Apex MCP is LeadShark’s LinkedIn MCP server, and it works as a custom connector in Claude.ai and through the hosted server in Claude Code. Claude gets 51 LinkedIn tools to find leads, read who engaged, comment, connect, DM and schedule posts, all inside the limits you set in the dashboard. Setup takes about a minute; see the LinkedIn MCP setup guide.

What is LeadShark’s LinkedIn MCP server?

Apex MCP is LeadShark’s LinkedIn MCP server. The server URL is https://apex.leadshark.io/mcp. It gives Claude, ChatGPT or Cursor 51 LinkedIn tools, and every write stays inside the same limits, pacing and approvals as the rest of your account.

What can the 51 tools do?

They follow a see, decide, act loop. Search people, companies and posts; turn a post’s commenters and reactors into a lead list; enrich a profile; comment, react, connect and DM as yourself; run comment-to-DM automations; and schedule posts. Pro+ is the MCP baseline and includes people and company search, post engagers and connection requests; post search, a person’s activity and acting as you are Apex.

Can Claude send LinkedIn DMs?

Yes, on Apex. With Apex MCP connected, Claude can DM a connection, or send an InMail with your own credits, from your own LinkedIn account. Every DM draws from the same daily limit as your automations, anywhere from 0 to 250 a day (we recommend a maximum of 150), and DMs to archived leads are refused at the send step. Leave write tools on Ask every time and Claude checks with you before each message.

Can Claude send connection requests?

Yes. Ask Claude to connect with someone and it sends the request from your own account; the MCP docs list connecting on Pro+ and Apex. Requests draw from the same daily and weekly connection caps as your automations, are paced like a person would send them, and with off-hours on they wait between 10 PM and 6 AM in your timezone.

How many connection requests can the agent send?

Up to 80 a day and 200 a week on all paid plans. The agent shares those caps with your automations, so a request Claude sends and one an automation sends count against the same budget. The agent can lower the cap or pause connecting, but raising it is staged for you to approve. For what LinkedIn itself says, see LinkedIn connection limit.

Can I post to LinkedIn from Claude?

Yes. Ask Claude to draft the post, then to schedule it for a date and time, and it lands in your LeadShark queue, with a comment-to-DM automation attached if you want one. You can list, edit, reschedule or cancel scheduled posts from the same chat. Scheduling is part of the Pro+ baseline, so it works on Pro+ and Apex.

Does Apex need my LinkedIn password?

No. LeadShark never asks for your LinkedIn email or password. You connect your LinkedIn account once with our extension, and from then on LeadShark runs in the cloud. Your assistant connects to LeadShark, not to your LinkedIn login. Claude, ChatGPT, Grok, Grok Bot, Cursor, Claude Code, Codex, OpenClaw and Hermes Agent connect to the hosted MCP server and sign in on apex.leadshark.io.

Do I need to install anything from GitHub?

No. Connect your assistant to https://apex.leadshark.io/mcp and sign in on apex.leadshark.io. Cursor, Claude Code and Codex also use this hosted server. No local LeadShark package or API key is needed, and there is no repository to clone or server to host.

What’s the Apex MCP server URL?

https://apex.leadshark.io/mcp. Claude.ai, ChatGPT, Grok, Grok Bot, Cursor, Claude Code, Codex, OpenClaw and Hermes Agent connect to this hosted server and sign in on apex.leadshark.io. Follow the setup steps for your assistant above.

Does it work with Claude Code?

Yes. Run claude mcp add --transport http leadshark https://apex.leadshark.io/mcp. Then run /mcp, select leadshark and sign in on apex.leadshark.io. Claude Code then gets the same tools, limits, pacing and approvals as Claude.ai. The account needs Pro+ or Apex.

Does it work with Cursor?

Yes. Add the URL configuration above to .cursor/mcp.json. Open Cursor Settings, then MCP, click Connect next to leadshark and sign in on apex.leadshark.io. The tools then show up for Cursor’s agent like any other MCP server, inside the same limits you set in the dashboard. The account needs Pro+ or Apex.

Does it work with Grok and Grok Bot?

Yes. In Grok, open https://grok.com/connectors, click New Connector, choose Custom and paste https://apex.leadshark.io/mcp. Sign in on apex.leadshark.io and approve access. In Grok Bot, ask "Add a custom MCP server called LeadShark at https://apex.leadshark.io/mcp", confirm with "Add it", then click Authorize on the connect card. Sign in on apex.leadshark.io and approve access. The account needs Pro+ or Apex.

Does it work with OpenClaw or Hermes Agent?

Yes. Both connect to the hosted server and sign in on apex.leadshark.io, so no API key is needed. In OpenClaw, run openclaw mcp set leadshark with the server URL, transport streamable-http and auth oauth, then openclaw mcp login leadshark with the Gateway stopped. In Hermes Agent, add leadshark under mcp_servers in ~/.hermes/config.yaml with url https://apex.leadshark.io/mcp and auth: oauth, then run hermes mcp login leadshark. After that you can ask from Telegram, WhatsApp, Slack or Discord. The account needs Pro+ or Apex.

Does it work with ChatGPT?

Yes. ChatGPT connects over OAuth with nothing to install: open Settings, then Apps, turn on Developer mode, create an app with the server URL and sign in with LeadShark Apex. Every write stays inside the same caps, pacing and approvals as the rest of your account.

Why don’t I see all the tools in Claude?

Claude keeps its own copy of a connector’s tool list. When we add or change tools, open the LeadShark Apex connector in Claude’s Connectors settings and refresh its tools list. Also check your plan: Pro+ sees 31 tools and Apex sees all 51.

Is the LinkedIn MCP free?

Try it free: start the 7-day free trial (no card) and unlock the one-time 72-hour Apex window in Settings to use the full MCP on your own posts before you pay. After that the MCP is part of Pro+ and Apex; Pro does not include it. Prices are on the pricing page.

How do I try the full MCP?

Start the 7-day free trial, no card, then unlock the one-time 72-hour Apex window in Settings and paste the server URL into your assistant. Ask it who engaged with your last post. Pro does not include the MCP; Pro+ is the baseline and Apex is the full agent. If you want the Apex tools without switching plans, see the Pro+ and Apex answer below.

What’s the difference between Pro+ and Apex for MCP?

Pro+ connects the MCP and covers your own content and pipeline: automations, scheduling, lead pages, people and company search, post engagers, connection requests, invitation triage, discovery and enrichment. Apex adds tools that read other people’s activity and act as you: post search, activity and inbox reads, signals, and commenting, reacting and DMing as yourself. Any account not already on Apex can unlock a one-time 72-hour Apex window in Settings to try the full agent.

What daily limits apply to the agent?

Sending stays inside a daily DM limit you set, anywhere from 0 to 250 a day (we recommend a maximum of 150), with human-like pacing, off-hours and warm-up mode. The agent uses the same caps as your automations. The full tool reference is in the Apex MCP docs.

Can the agent raise its own sending limits?

No. It can check what’s left, lower a cap or pause a channel immediately. Raising a cap is staged for you to approve. DMs, comment replies and connection requests all draw from the same caps you set in the dashboard.

Can I stop every agent action at once?

Yes. Emergency Stop, under Agent, then Logs in the dashboard, blocks every agent write on the account instantly: automations, MCP, everything. Reads keep working until you resume.

Try it with your own agent

Start the 7-day free trial, no card, then unlock the one-time 72-hour Apex window in Settings and paste the server URL into your assistant. Ask who engaged with your last post. Keep write tools on “ask every time” for the first week.

Prefer to ask about comment-to-DM first? Ask Claude · How to connect