What is the Reachium LinkedIn MCP server?
A remote MCP server that gives your AI client access to a LinkedIn
workspace. Streamable HTTP, OAuth 2.1 with Dynamic Client Registration
and PKCE. No local install, no Chrome extension, no proxy.
Endpoint: https://app.reachium.io/api/mcp
Quickstart (Claude)
claude mcp add --transport http reachium https://app.reachium.io/api/mcp
Your browser opens for OAuth, you pick a scope, and the tools appear.
76 tools, three scopes
| Scope | Tools | What it can do |
|---|
| read | 33 | Campaign stats, funnels, leads, inbox, post analytics |
| write | 70 | Draft campaigns, edit sequences, manage leads and content |
| launch | 76 | Adds the 6 tools that can reach another person |
The launch scope is the only one that can send: sendMessage,
sendReply, activateCampaign, schedulePost, scheduleSlot,
startScrape. Everything else is read or draft.
Safeguards
Agents make mistakes, so sending is gated twice.
- Preview and confirm. The first call to any launch tool returns a
preview and a signed token valid for 5 minutes. Nothing sends until
the model calls again with that token.
- Daily caps. Hard per-workspace ceilings (75 posts, 50 DMs, 50
replies a day) reserved before the mutation, so a runaway loop stops.
Every call writes an audit row with the key id and the records it
touched, so "an agent sent 200 DMs, who authorised that?" has an answer.
Rate limits are 600/min per IP and 120/min per key. Keys are scoped and
revocable.
Full tool list and docs: https://www.reachium.io/linkedin-mcp-server
Comments