MCP.so
Sign In

Reachium LinkedIn MCP ServerVerifiedFeatured

@Reachium

Basic information

Transport

streamable-http

Authentication

OAuth

Category

Productivity

Author

Reachium

Submitted by

Vincent Nebeling

About Reachium LinkedIn MCP Server

A remote LinkedIn MCP server. Connect Claude to LinkedIn and run campaigns, content, leads and inbox through 80+ tools — with scoped keys, preview-and-confirm before anything sends, and hard daily caps.

Connection details

https://app.reachium.io/api/mcp

Setup

claude mcp add reachium-linkedin --transport http https://app.reachium.io/api/mcp

Reachium LinkedIn MCP Server tools

Tool list not available yet

This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.

This server requires authentication. Tool discovery may require signing in or credentials from the provider.

Fetch the live tool list directly from this server's endpoint using the button above.

Overview

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

ScopeToolsWhat it can do
read33Campaign stats, funnels, leads, inbox, post analytics
write70Draft campaigns, edit sequences, manage leads and content
launch76Adds 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.

  1. 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.
  2. 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

Frequently asked questions

1

What is the Reachium LinkedIn MCP Server remote MCP server?

The Reachium LinkedIn MCP Server remote MCP server is a hosted Model Context Protocol endpoint at https://app.reachium.io/api/mcp, so AI assistants can connect to it without installing or running anything locally.

2

How do I connect to the Reachium LinkedIn MCP Server MCP server?

Add the endpoint https://app.reachium.io/api/mcp to any MCP-compatible client such as Claude Code, Cursor, or VS Code. The setup snippets on this page configure each client in one step.

3

Does the Reachium LinkedIn MCP Server MCP server require authentication?

Yes. Reachium LinkedIn MCP Server uses OAuth: the first time you connect, your MCP client opens a browser window to sign in and authorize access, then reuses the credentials for future sessions.

4

Which transport does the Reachium LinkedIn MCP Server MCP server use?

Reachium LinkedIn MCP Server exposes a streamable-http endpoint, the transport used by remote MCP servers and supported by all major MCP clients.

Comments