mcpbeat Sign in

Linkedin MCP Server

answering

Linkedin is answering right now. Last checked 9 min ago.

LinkedIn campaigns, content, leads and inbox from your AI client. Scoped, revocable keys.

Uptime history 19 days of history · worst day 99%
19 days agonow
100.0%
Uptime 24h
92 of 92 checks
—
Tools
hidden behind auth
335 ms
Response time
average over 24h
OAuth sign-in
Access
streamable-http

Nothing serious here today

Today is the operative word: we check Linkedin every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 9 min ago.

run in your terminal
claude mcp add linkedin --transport http https://app.reachium.io/api/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "linkedin": {
      "url": "https://app.reachium.io/api/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.linkedin]
url = "https://app.reachium.io/api/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "linkedin": {
      "url": "https://app.reachium.io/api/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "linkedin": {
      "url": "https://app.reachium.io/api/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

Endpoints

URLTransportStateLatencyChecked
https://app.reachium.io/api/mcp streamable-http sign-in 264 ms 9 min ago

Alternatives to Linkedin

same job, measured the same way
LinkedNav
by linglistack

Run LinkedIn outreach from your AI chat: find leads, launch campaigns, send, and reply.

answering
Campaignstack
by campaignstack

Run B2B outreach from your AI agent: 250+ tools for campaigns, leads, LinkedIn and email workflows.

answering
Qampi
by shivasingh9927

LinkedIn outreach from your agent: find prospects, add leads, run campaigns, read results.

215 installs/wk local only
Omentir
by vanshyadav1408

Find LinkedIn prospects, draft outreach, and run human-paced campaigns from your AI agent.

answering
Onsa
by onsa

Find scored B2B leads, read campaign replies and send approved LinkedIn outreach.

16 tools answering
Crispy
by crispy

Full LinkedIn access for AI agents: leads, messaging, and campaigns with safe limits built in.

answering
ZenMode
by zenmode87

Read LinkedIn outreach campaigns, contacts and replies, and manage campaign leads and targeting.

answering
Adside
by adside

AI agents that manage paid ads on Meta, LinkedIn, and Google Ads from any MCP client.

answering

Linkedin — questions

Answers built from our own checks of this server.

Why is there no tool list for Linkedin?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.
Is Linkedin working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 335 ms. The bar chart above shows every period we have measured.
How do I connect Linkedin?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.
How do you sign in to Linkedin?
No API key is involved. Linkedin answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.
How fast is Linkedin?
It answers our handshake in 335 ms on average, which is faster than 41% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.