H
Official Finance & Sales

HeyReach

Manage LinkedIn outreach campaigns, leads, and replies from HeyReach.

Works with: Claude DesktopClaude CodeCursorWindsurf

How to install the HeyReach MCP server

Add this to your Claude Desktop MCP configuration:

Native remote server. Connect via mcp-remote using your per-workspace HeyReach URL and API key.

Add this to your Claude Code MCP configuration:

Native remote server. Connect via mcp-remote using your per-workspace HeyReach URL and API key.

Add this to your Cursor MCP configuration:

Native remote server. Connect via mcp-remote using your per-workspace HeyReach URL and API key.

Add this to your Windsurf MCP configuration:

Native remote server. Connect via mcp-remote using your per-workspace HeyReach URL and API key.

Built by ContextBoltThis directory is built by ContextBolt: MCP-native memory and SEO tools that run alongside HeyReach in the same client.

Explore ContextBolt

HeyReach’s MCP server connects an AI agent to your HeyReach workspace so you can run LinkedIn outreach from a chat window. You can check on campaigns, pull lead lists, and review replies in plain language instead of clicking through the dashboard. It is aimed at agencies and sales teams already using HeyReach for LinkedIn sequences.

Why use it

Outreach work is a lot of small status checks and follow-ups. This server lets you ask about campaign performance, find leads that match a condition, and surface conversations that need a human reply, all without leaving your editor. For anyone juggling several client campaigns, that is a faster way to triage than switching tabs.

What it actually does

  • ‘Which of my campaigns have the highest reply rate this week?’
  • ‘List leads who replied but have not been followed up.’
  • ‘Show me new replies across all active campaigns.’

It reads and manages campaigns, leads, and replies inside a single HeyReach workspace.

Gotchas

This is a native remote server, so you connect through mcp-remote using a per-workspace URL plus your API key. Each workspace has its own URL, which matters if you manage several clients. It only reaches data inside HeyReach, not LinkedIn directly, so anything not synced to your workspace is out of scope. As with any outreach automation, keep your sending within LinkedIn’s limits; the server does not shield you from platform restrictions.

Built by ContextBolt

This directory is built by ContextBolt

We build MCP-native tools that give your AI the context it cannot reach on its own. Bookmarks turns your saved posts into agent-queryable memory. SEO puts live keyword and ranking data inside Claude. Both run alongside HeyReach in the same client.

Explore the products →

HeyReach MCP server: FAQs

Is this an official HeyReach server?

Yes. It is HeyReach's own native remote MCP server, connected with a per-workspace URL and API key.

How do I connect it?

It is a remote server, so you use mcp-remote with your workspace URL and API key. Each HeyReach workspace has a distinct URL, so use the one for the workspace you want.

Does it interact with LinkedIn directly?

No. It works with data inside your HeyReach workspace, such as campaigns, leads, and replies. LinkedIn activity still flows through HeyReach itself.

Can I manage multiple client workspaces?

Yes, but each workspace has its own URL and key. To switch clients you point the connection at the relevant workspace credentials.

Will it protect me from LinkedIn sending limits?

No. It surfaces and manages your outreach, but you are still responsible for keeping activity within LinkedIn's limits and HeyReach's own guardrails.