HeyReach

io.heyreachPublished by heyreach.ioOfficial publisherv1.0.1Updated Oct 24, 2026

Automate your HeyReach workspace — manage campaigns, leads, unibox, webhooks, and pull analytics.

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

Lets an assistant manage a HeyReach workspace: campaigns, leads, unibox, webhooks, and analytics.

What you can do
HeyReach exposes its workspace through a remote MCP endpoint. According to the registry description, an assistant can automate campaigns, manage leads, work with the unibox, configure webhooks, and pull analytics. No individual tools are listed in the manifest, so the exact operations are not documented here.
When to use it
Useful when you already run outreach in HeyReach and want an assistant to handle campaign and lead work, unibox follow-ups, webhook setup, or reporting without switching to the app.
Requirements
A remote MCP endpoint at using streamable HTTP. It requires a workspace-scoped MCP key generated in the HeyReach app, sent in the X-MCP-KEY header. No local runtime, packages, or environment variables are declared.
Before you install
The X-MCP-KEY header carries a secret workspace-scoped key; keep it private and scope it to the workspace you intend. The server can change campaign, lead, unibox, and webhook data, so assistant actions may modify or send outreach data. Review write actions before allowing them.

Installation

In SourceWeft

  1. Open HeyReach in the dashboard and add it to a workspace.
  2. Connect X-MCP-KEY 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/io.heyreach%2Fmcp/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": {
    "heyreach": {
      "type": "http",
      "url": "https://mcp.heyreach.io/mcp",
      "headers": {
        "X-MCP-KEY": "<YOUR_API_KEY>"
      }
    }
  }
}

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.1LatestSep 24, 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.