mcpbeat

Linkedin Posts MCP Server

io.github.johnisanerd/linkedin-posts
answering

Linkedin Posts is answering right now. Last checked 10 min ago. Last commit 3 Aug 2026.

Scrape and analyze public LinkedIn posts as structured JSON via the Apify LinkedIn Posts API.

Uptime history 40 hours of history
40 hours agonow
100.0%
Uptime 24h
91 of 91 checks
—
Tools
hidden behind auth
425 ms
Response time
average over 24h
0
Stars
last commit 3 Aug 2026

Connect this server

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

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

This endpoint answered with an authorization challenge — the server is running, but you need an API key or OAuth to use it.

Endpoints

URLTransportStateLatencyChecked
https://mcp.apify.com/?tools=johnvc/linkedin-posts-api streamable-http needs key 459 ms 10 min ago

Linkedin Posts — questions

Answers built from our own checks of this server.

Why is there no tool list for Linkedin Posts?
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 Posts working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 425 ms. The bar chart above shows every period we have measured.
How do I connect Linkedin Posts?
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 will need your own key or an OAuth login: it refuses anonymous clients.
Does Linkedin Posts need an API key?
Yes. Every time we knock, Linkedin Posts answers with an authorization challenge instead of its tool list — that is how we know it is running and gated rather than broken. Bring your own credentials and it will talk.
How fast is Linkedin Posts?
It answers our handshake in 425 ms on average, which is faster than 30% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is Linkedin Posts open source?
Yes — written in Python and 0 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.