Reach MCP — LinkedIn for AI agents

com.reachmcpPublished by reachmcp.comOfficial publisherv1.1.0Updated Oct 24, 2026

LinkedIn for AI agents: inbox, invitations, Sales Navigator search, posts, jobs, quotas, webhooks.

VerifiedStreamable HTTPWeb executableCommunication & CollaborationBusiness & Commerce

Overview

AI-generated overview

Lets an assistant work a LinkedIn account: inbox, invitations, Sales Navigator search, posts, jobs, quotas and webhooks.

What you can do
Connects an AI assistant to a LinkedIn account through a hosted remote endpoint. The described scope covers the inbox, invitations, Sales Navigator search, posts and jobs, plus quotas and webhooks. It is aimed at agents that handle LinkedIn outreach and content tasks rather than general web browsing.
When to use it
Use it when an assistant should read or act on LinkedIn activity: triaging the inbox, managing invitations, running Sales Navigator searches, publishing posts, or tracking jobs. It fits outreach and recruiting workflows where LinkedIn is the working surface. Skip it if the assistant only needs general web search or non-LinkedIn messaging.
Requirements
A remote streamable HTTP endpoint at app.reachmcp.com; nothing is installed locally. Authentication is required: OAuth clients sign in through a Reach page, while clients without OAuth need an X-API-Key header value created in the Reach app on the API & MCP page. Network access to the endpoint is needed.
Before you install
It acts on a live LinkedIn account: inbox, invitations, posts and jobs can be read and changed, so review what the assistant is allowed to send or modify. Access is granted through OAuth or an X-API-Key secret created in the Reach app; treat that key as a credential and keep it out of shared logs. Quotas and webhooks are mentioned, so check plan limits and where event data is delivered before enabling.

Installation

In SourceWeft

  1. Open Reach MCP — LinkedIn for AI agents in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.reachmcp%2Flinkedin/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "reach-linkedin-for-ai-agents": {
      "type": "http",
      "url": "https://app.reachmcp.com/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

2
  1. v1.1.0LatestSep 27, 2026
  2. v1.0.0Sep 16, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.