Pro Reach LinkedIn Outreach

ai.proreachPublished by proreach.aiOfficial publisherv1.0.0Updated Oct 28, 2026

Plan and run LinkedIn outreach: templates, leads, confirmation-gated launch, metrics, replies.

VerifiedStreamable HTTPWeb executableCommunication & CollaborationBusiness & Commerce

Overview

AI-generated overview

Remote Pro Reach MCP server that lets an assistant plan and run LinkedIn outreach campaigns: templates, leads, confirmation-gated launch, metrics and replies.

What you can do
  • Plan LinkedIn outreach campaigns and prepare them for launch
  • Work with message templates and lead lists
  • Launch campaigns only after an explicit confirmation step
  • Review campaign metrics and incoming replies
When to use it
Useful when you run LinkedIn outreach through Pro Reach and want an assistant to help draft templates, assemble leads, check performance and follow up on replies without leaving the chat.
Requirements
A remote streamable HTTP endpoint at proreach.ai, reachable over the network. A Pro Reach account and a bearer API key sent in the Authorization header; the key is created in Pro Reach under Settings, then AI agents (MCP).
Before you install
The Authorization header carries a secret API key, so keep it out of shared logs and chats. Launching campaigns can send real messages to real people and may consume paid plan capacity; rely on the confirmation gate before anything goes out. Replies and lead data are handled by Pro Reach as a third party.

Installation

In SourceWeft

  1. Open Pro Reach LinkedIn Outreach in the dashboard and add it to a workspace.
  2. Connect Authorization token 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/ai.proreach%2Foutreach/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.

{
  "mcpServers": {
    "pro-reach-linkedin-outreach": {
      "type": "http",
      "url": "https://proreach.ai/api/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

56% 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

    Publish an icon in the registry entry.

  • 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.