HeyReach MCP Server: What It Exposes, Setup and Limits

HeyReach has an official MCP server that lets an AI client such as Claude work inside your HeyReach workspace: build a campaign, change its sequence, schedule and senders, and start it. HeyReach says it costs nothing extra and lists it on every paid plan. Setup is documented step by step for Claude on the web and Claude Desktop; other clients are named but, in the pages we could read, not documented, and HeyReach publishes no MCP limits or permission controls.

Some tool links here are affiliate links (disclosure). To follow along you need a workspace: start a HeyReach trial (HeyReach says 14 days, 3 LinkedIn accounts, no card). For pricing, features and weaknesses of the product as a whole, read our HeyReach review.

Nerdy Joe is a certified Apollo.io Managed Services Partner and a PlusVibe Certified Silver Partner, and we are a HeyReach affiliate. We did not connect the HeyReach MCP server for this guide. The steps and tool names come from HeyReach's MCP page, help center and blog, checked November 11, 2026.

HeyReach MCP quick facts

What the HeyReach MCP server is

MCP stands for Model Context Protocol. HeyReach describes it as a protocol "that allows your AI apps to securely interact with tools", and says that with its server "you can connect any AI LLM to your workspace."

In plain terms, your AI client gets a set of HeyReach actions it can call during a chat. You ask for something in normal language, the client picks the tool, and HeyReach carries it out in the workspace the key belongs to.

It sits beside two other developer routes. The REST API does the same campaign work through HTTP calls, covered in our HeyReach API guide, and HeyReach also has a CLI. MCP is the route for people who want to stay in a chat window and write no code.

One point of confusion to clear up: third-party MCP wrappers and npm packages for HeyReach exist. They are not made by HeyReach. This guide covers only the official server you enable inside the product.

What it exposes: the confirmed tools

HeyReach announced 8 campaign tools on June 12, 2026. These are the only tool names we can confirm from HeyReach's own pages.

Together these cover a campaign from blank draft to live. They map closely to the campaign endpoints in the public API, where HeyReach documents that only draft, scheduled and paused campaigns can be updated.

What else the server does

HeyReach's MCP page describes more than campaign building. It lists task types: launch campaigns, draft messages, assess performance, act on warm leads, segment leads and report on pipeline.

The page gives no tool names for those tasks, and we found no full tool list or tool count on the pages we read. So we will not publish one. Two smaller details are documented: blacklist requests through MCP are capped at 100 rows, and voice note endpoints are "coming in v2".

The reliable way to see the real list is inside your client. Once connected, most MCP clients show every tool the server offers, with descriptions, before you run anything.

Supported AI clients

HeyReach names clients in two places, and the lists differ.

So the honest answer on ChatGPT and Cursor is this: HeyReach says they work, and we could not find HeyReach's steps for them. The general pattern (paste the MCP Connection URL where the client asks for a remote MCP server) should apply, but that is our inference and not a documented procedure.

Setup as documented

Step 1: create the MCP key in HeyReach

HeyReach's help center gives the same first steps for every client.

1. Open your workspace in HeyReach.
2. Go to Integrations, then HeyReach MCP Server.
3. Click "New MCP Key". The key and the "MCP Connection URL" appear.
4. Copy the MCP Connection URL.

Each workspace has its own key and URL. You can generate a new key at any time, and HeyReach says the connection URL updates when you do, which also means any client using the old URL needs the new one.

HeyReach shows the URL format only as a placeholder in its docs, so we do not print one here. Copy yours from the app.

Step 2a: Claude on the web

These are the steps in HeyReach's Claude article (dated October 4, 2025).

1. In Claude, go to Settings, then Connectors, then Add Custom Connector.
2. Name it "HeyReach MCP" and paste the MCP Connection URL.
3. Click Add. HeyReach says Claude takes a few seconds to connect.
4. When prompted, paste the API key from your HeyReach workspace settings.
5. Before you start a chat, make sure the HeyReach MCP toggle is on in Claude.

HeyReach does not state which Claude plans support custom connectors, and Claude's menus change, so check Anthropic's current connector docs if a menu name differs.

Step 2b: Claude Desktop

HeyReach's steps for the desktop app use a config file.

1. Close Claude Desktop.
2. Open claude_desktop_config.json. On Windows it is at %APPDATA%\Claude\claude_desktop_config.json. On macOS it is at ~/Library/Application Support/Claude/claude_desktop_config.json.
3. Add the entry below, replacing the placeholder with your MCP Connection URL.
4. Save the file and restart Claude Desktop.

{
  "mcpServers": {
    "heyreach": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "<YOUR_HEYREACH_MCP_CONNECTION_URL>"
      ]
    }
  }
}

This is the config HeyReach documents. It runs npx, so the machine needs Node.js installed; HeyReach's article does not state a version.

Other clients

For Clay, Visual Studio Code and Make, HeyReach has help articles that we did not read, so follow those directly. For ChatGPT, Cursor, OpenClaw and anything else, HeyReach's readable pages give no steps. Treat any walkthrough you find elsewhere as unofficial.

A security note on the URL

HeyReach says "MCP endpoints include built-in authentication for secure, reliable connections." The mechanism its help center names is the MCP Key, which is part of the connection URL, plus the workspace API key for the Claude web connector.

That makes the URL itself a credential. Do not paste it into shared documents, screenshots or a public repository, and generate a new key if it leaks.

Example uses

HeyReach's own example prompts

These three are published by HeyReach. We did not run them.

• "Pull last week's positive replies and draft personalized follow-ups for each."
• "Segment my leads by company size and only message the 200+ employee accounts."
• "Clone my best-performing campaign, swap in this lead list, assign my three warmest senders, set it to send 9-5 CET on weekdays, and launch it."

Note the last word of the third prompt. HeyReach's own example ends with the AI launching the campaign.

Our illustrations

The prompts below are our illustrations of how the 8 confirmed tools could be used. They are not HeyReach output and we did not test them.

Use GetCampaignSequence to show me the sequence for my "Q4 Agency Owners" campaign.
List each step, the delay before it and the message text. Do not change anything.

Clone "Q4 Agency Owners" with CreateCampaignFromTemplate and name the copy
"Q4 SaaS Founders". Leave it in draft. Show me the settings and the sequence, and
do not call StartCampaign until I reply "launch".

In the draft "Q4 SaaS Founders", rewrite the first follow-up message to be under
400 characters and plainer. Show me the old and new text side by side before you
call UpdateCampaignSequence.

Update the schedule on the draft "Q4 SaaS Founders" to weekdays, 9am to 5pm
Eastern. Then read the campaign back to me so I can check it.

The pattern in all four: read first, show the change, wait for a yes. It costs one extra message and removes most of the ways an agent can surprise you.

Limits and what is not published

The MCP server makes HeyReach easy to drive from a chat. These are the limits to know before you hand it real senders.

• It can start live campaigns. StartCampaign exists, so a connected AI client can put messages in front of real people from real LinkedIn accounts. HeyReach publishes no read-only mode for MCP on the pages we read.
• No published MCP rate limits. The public API is limited to 300 requests a minute; whether MCP shares that limit is not stated.
• No published permission scoping or audit log. HeyReach has role permissions for human members, but nothing we read says how they apply to an MCP key.
• No full tool list. Only the 8 campaign tools are named.
• Setup is documented for few clients. Claude is covered in detail. ChatGPT and Cursor are named without steps we could find.
• One key per workspace. An agency with many client workspaces manages many URLs, and it is easy to connect the wrong one. HeyReach's own note says to use the correct workspace's values.
• Rotating the key changes the URL. Every client using it must be updated.
• Updates replace, they do not patch. In the API, a sequence update fully replaces the sequence and a sender update replaces the full list. Assume the matching MCP tools behave the same way and ask the agent to read back the result.
• Active campaigns are not editable. Per HeyReach's Campaign API post, only draft, scheduled and paused campaigns can be updated.
• Voice notes are not available through MCP yet ("coming in v2").

The full HeyReach review covers the wider product limits that also apply here, such as HeyReach not sending email and the Agency and Unlimited plans requiring your own proxies.

The LinkedIn caution

An AI agent that can launch campaigns makes this section more relevant, not less. LinkedIn's User Agreement restricts bots and other automated methods for adding contacts and sending messages, and LinkedIn's help center has a page titled Prohibited software and extensions. Our tools could not open LinkedIn's pages, so we paraphrase and link them and do not quote them.

HeyReach itself says LinkedIn's User Agreement bans software that automates connecting and messaging, and states that it is not associated with or endorsed by LinkedIn. HeyReach says its per-sender limits and dedicated proxies reduce the risk of an account restriction. No vendor can remove that risk, and HeyReach's terms place the consequences of third-party platform action on the customer.

MCP does not change any sending limit. HeyReach says daily limits are set per sender, and an agent that creates five campaigns on one account shares that account's limit across all five. Our guide on whether HeyReach is safe covers the stated limits and what nobody can promise.

A safe way to work with it

This checklist is our advice, built from the documented behavior above.

• Connect a test workspace first, not your largest client's.
• Ask the client to list the HeyReach tools it sees before you run anything.
• Put "leave it in draft" and "do not call StartCampaign" in every build prompt.
• Have the agent read the campaign back (GetCampaignSequence) after each change.
• Check senders, lead list, exclusions and schedule in the HeyReach app before you start.
• Start campaigns yourself, in the app, until you trust the workflow.
• Keep the connector toggle off in Claude when you are not using it.
• Generate a new MCP key when someone with access leaves.

Who the HeyReach MCP server fits

• Best for: operators who already work in Claude and run several HeyReach campaigns, and want to clone, edit and stage campaigns by describing them.
• Best for: agencies that build similar campaigns for many clients, where "clone this, swap the list and senders" is the daily job.
• Best for: teams testing agent workflows who are happy to keep a human on the launch step.
• Not ideal for: teams that need documented read-only access, scoped permissions or an audit trail for AI actions.
• Not ideal for: ChatGPT or Cursor users who want official step-by-step setup today.
• Not ideal for: anyone who wants the agent to source and verify leads too. HeyReach's tools manage campaigns; the list comes from elsewhere.

On that last point, lead data usually comes from a separate tool. Our MoltSets MCP server guide covers one data source built for AI clients, and our guide to email and LinkedIn outreach for agencies covers how the channels fit together. If cost per sender is the open question, see HeyReach pricing.

Final take

The HeyReach MCP server is a real, official way to run LinkedIn campaign building from Claude: one key, one URL, and 8 confirmed tools that take a campaign from draft to live. It is included on paid plans at no extra charge, per HeyReach.

What it lacks is published guardrails. There are no documented MCP rate limits, no scoping and no full tool list, and setup is written up for Claude far more thoroughly than for anything else. Keep a human on the launch step and it is a useful time saver.

To try it, open a HeyReach trial, create an MCP key in a test workspace and connect Claude with the steps above. If it fits how you work, choose a HeyReach plan by sender count.

For plans, features, safety and alternatives in one place, read the complete HeyReach review. When you are ready, connect HeyReach to your AI client.

Rather not build the list yourself?

Nerdy Joe is owned by Agency Growth Partners (AGP). AGP builds verified lead lists and runs outbound for agencies, including LinkedIn campaigns like the ones described above. If you would rather hand it off, book a call with David.

Sources

• HeyReach MCP page: https://www.heyreach.io/mcp
• HeyReach help, how HeyReach MCP works with popular tools: https://help.heyreach.io/en/articles/12117291-how-does-heyreach-mcp-work-with-popular-tools
• HeyReach help, integrating HeyReach MCP with Claude (October 4, 2025): https://help.heyreach.io/en/articles/12123398-how-to-integrate-heyreach-mcp-with-claude
• HeyReach blog, MCP campaign tools (June 12, 2026): https://www.heyreach.io/blog/heyreach-mcp-build-and-launch-campaigns-end-to-end
• HeyReach blog, Campaign API (April 21, 2026): https://www.heyreach.io/blog/campaign-api
• HeyReach API documentation (Postman): https://documenter.getpostman.com/view/23808049/2sA2xb5F75
• HeyReach blog, Blacklist: https://www.heyreach.io/blog/blacklist-is-live
• HeyReach CLI: https://www.heyreach.io/cli
• HeyReach help, roles and permissions: https://help.heyreach.io/en/articles/11782284-how-to-invite-team-members-and-manage-role-based-permissions-in-heyreach
• HeyReach help, sender rotation: https://help.heyreach.io/en/articles/9897768-multiple-linkedin-senders-in-one-campaign-sender-rotation
• HeyReach blog, LinkedIn company page removal: https://www.heyreach.io/blog/heyreach-ban
• HeyReach pricing: https://www.heyreach.io/pricing
• HeyReach terms of service: https://www.heyreach.io/terms-of-service
• LinkedIn User Agreement (linked, not readable to our tools): https://www.linkedin.com/legal/user-agreement
• LinkedIn Help, Prohibited software and extensions (linked, not readable to our tools): https://www.linkedin.com/help/linkedin/answer/a1341387