Apex by LeadShark

LinkedIn MCP for Claude, ChatGPT and Cursor

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 trial, no card. Or unlock a one-time 72-hour Apex window in Settings. See plans.

Apex MCP server URL

https://apex.leadshark.io/mcp

Paste it into Claude.ai or ChatGPT. For Cursor and Claude Code, use the local package with an API key. Full MCP docs.

Connect in minutes

Claude.ai and ChatGPT use OAuth, so there's nothing to install. Cursor and Claude Code run a local package. Step-by-step notes are in the setup guide.

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.

Cursor / Claude Code

Local package · API key from Settings

1. Create an API key in LeadShark Settings. You’ll need Node.js 18 or newer.
2. In Cursor, add the LeadShark server to.cursor/mcp.json and restart.
3. In Claude Code, one command adds it: claude mcp add leadshark with your key.

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

Cursor ·.cursor/mcp.json

{
  "mcpServers": {
    "leadshark": {
      "command": "npx",
      "args": ["-y", "@leadshark/mcp-server"],
      "env": {
        "LEADSHARK_API_KEY": "${LEADSHARK_API_KEY}"
      }
    }
  }
}

Claude Code

claude mcp add leadshark \
  --transport stdio \
  --env LEADSHARK_API_KEY=your_key \
  -- npx -y @leadshark/mcp-server

See, decide, act

Apex MCP exposes 47 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.

Apex

Search people, companies and posts

Find ICP-fit people or companies, and posts by keyword, then act on what you find.

Apex

Turn engagement into a lead list

Read a post’s commenters and reactors, or a person’s recent comments and reactions.

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, connect, reply to a comment, and send a DM, or an InMail with your own credits.

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.

Ask it in plain language

• Who engaged with my last post? Build me a lead list, warmest first.
• What has Jane Doe been commenting on lately? Draft a connection note and check we haven’t talked before.
• Schedule my guide post for Tuesday 9am and DM anyone who comments “guide”.
• What have you already done today? Anything refused or waiting for approval?
• Set my daily DM limit to zero.

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.7M

Total DMs delivered

3M

Comments captured

<10m

Average response time

2.7M+ DMs and 3M 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, invitation triage, discovery and enrichment. Apex adds 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.

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.

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 47 LinkedIn tools, and every write stays inside the same limits, pacing and approvals as the rest of your account.

What can the 47 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; tools that read or act on other people are Apex.

What’s the Apex MCP server URL?

https://apex.leadshark.io/mcp. Paste it into Claude.ai under Customize, then Connectors, or into ChatGPT under Settings, then Apps with Developer mode on and Authentication set to OAuth. Cursor and Claude Code use the local @leadshark/mcp-server package with an API key from your LeadShark settings.

How do I try the full MCP?

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, then paste the server URL into your assistant. Pro does not include the MCP; Pro+ is the baseline and Apex is the full agent.

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.

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.

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, invitation triage, discovery and enrichment. Apex adds tools that read and act on other people: search, engagers, activity, inbox, and commenting, connecting and DMing as yourself.

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.

Try it with your own agent

Create a LeadShark account, start the 72-hour Apex trial, paste the server URL into your assistant, and 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