Productivity · Remote MCP server
Reach MCP - LinkedIn for AI agents
LinkedIn for AI agents: inbox, invitations, Sales Navigator search, posts, jobs, quotas, webhooks.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
com.reachmcp/linkedin- Version
- 1.1.0
- Status
- Active
- Category
- productivity
- Transport
- Streamable HTTP
- Published
- 2026-09-27
- Updated
- 2026-09-27
- Publisher
- com.reachmcp
- Namespace
- Namespace verified by the MCP Registry via the domain reachmcp.com · how
- Listed under
- LinkedIn MCP servers
- Website
- www.reachmcp.com
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://app.reachmcp.com/mcp | X-API-Key (secret) |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
- Checked on
- 2026-10-05
How to connect Reach MCP - LinkedIn for AI agents
Reach MCP - LinkedIn for AI agents is a remote MCP server: there is nothing to install. Its endpoint is https://app.reachmcp.com/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
The registry entry declares an HTTP header for the connection: X-API-Key (secret). A secret header usually carries an API key or token issued by the service; clients that accept custom headers set it with the server's URL.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More productivity servers
| Server | Runs |
|---|---|
| RCS CampaignsSend RCS & SMS campaigns: templates, audiences, surveys, inbox replies, delivery webhooks. | Local · stdio |
| RD StationRD Station Marketing, contacts/leads (get, upsert, funnel), conversion events and webhooks via the o. | Remote · HTTPLive check: ✓ handshake |
| Rdstation Crm MCPManage RD Station CRM contacts, deals, tasks and notes, with pipeline health reports. | Local · stdio |
| Re:port Flow MCPGenerate PDF reports from Re:port Flow templates via Claude and other AI agents. | Remote & Local · HTTP, stdioLive check: ✓ handshake |
| Reactive ResumeFree open-source resume builder with remote MCP tools for resumes and job applications. | Remote · HTTPLive check: sign-in required |
| ReassignReassign: a circular 24-hour calendar and time-tracking copilot with ADHD-friendly scheduling. | Remote · HTTPLive check: sign-in required |
| RebarEvent-sourced ticket tracker + Jira reconciler, exposed as a Python library, CLI, and MCP server. | Local · stdio |
| RecallNotes, files, GitHub, and Drive through one MCP connection. | Remote · HTTPLive check: sign-in required |