LinkedIn MCP servers in 2026.Which ones post, and which ones scrape.

The kinds of LinkedIn MCP serverHow each one gets to your account.

What LinkedIn's API lets a server doThe rules every server works within.

• Post as yourselfThe w_member_social permission, granted by the Share on LinkedIn product, lets an app post text, links, images and video as the member who signed in. It's self-serve, limited to 150 requests per member per day.
• Post as a Company PageOnly through the Community Management API, which LinkedIn calls a vetted product: a development tier first, then a standard tier that needs a screencast of each use case. That's why most tools, Breakreach included, post to personal profiles only.
• Read your own post statsMember post statistics sit behind the same vetted API, and r_member_social, the permission to read your own posts, is closed to new requests, per LinkedIn. That's why Breakreach doesn't report LinkedIn stats yet.
• Profiles, jobs, messagesNone of these is open to a regular app. A server that offers them is driving a browser.

In Claude Code, Cursor or any MCP clientOne hosted server, OAuth or an API key.

The server lives at https://api.breakreach.com/mcp and speaks Streamable HTTP, so there is nothing to install. Clients that handle OAuth sign you in; others send an API key from Settings → API & MCP.

claude mcp add --transport http breakreach https://api.breakreach.com/mcp

{
  "mcpServers": {
    "breakreach": {
      "url": "https://api.breakreach.com/mcp",
      "headers": { "Authorization": "Bearer br_YOUR_API_KEY" }
    }
  }
}

What to askThree requests that work on LinkedIn today.

• “Turn these notes into a LinkedIn post under 1,300 characters, no hashtags”
• “Make the first line a sharper hook and schedule it for Tuesday at 9 AM”
• “Write the same launch for LinkedIn and X, each in its own tone, and post both tomorrow morning”