Modern MCP server for HeyReach LinkedIn automation with dual transport support (stdio + HTTP streaming) and header authentication
Heyreach MCP MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. Modern MCP server for HeyReach LinkedIn automation with dual transport support (stdio + HTTP streaming) and header authentication.
A modern Model Context Protocol (MCP) server with dual transport support for HeyReach LinkedIn automation. Supports both local (stdio) and remote (HTTP streaming) connections for maximum flexibility.
Once Heyreach MCP is connected, these are the calls the assistant has available:
Command — line arguments** (Claude Desktop): --api-key=YOUR_API_KEYRailway — The Railway tool exposed by this serverMessaging — The Messaging tool exposed by this serverAnalytics — The Analytics tool exposed by this serverPrerequisites — The Prerequisites tool exposed by this serverSetup — The Setup tool exposed by this serverTesting — The Testing tool exposed by this serverheyreach-mcp-server on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.
You will need 5 environment variables: YOUR_MCP_SERVER_URL, YOUR_HEYREACH_API_KEY, YOUR_API_KEY, CUSTOM_URL, HEYREACH_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Among the team communication options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Heyreach MCP's toolset — Command, Railway, Messaging and 4 more — is a fair guide to whether it matches your workflow. It is maintained by bcharleson; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| Command | line arguments** (Claude Desktop): --api-key=YOUR_API_KEY |
| Railway | The Railway tool exposed by this server. |
| Messaging | The Messaging tool exposed by this server. |
| Analytics | The Analytics tool exposed by this server. |
| Prerequisites | The Prerequisites tool exposed by this server. |
| Setup | The Setup tool exposed by this server. |
| Testing | The Testing tool exposed by this server. |
{
"mcpServers": {
"heyreach": {
"command": "npx",
"args": [
"heyreach-mcp-server@2.0.0",
"--api-key=YOUR_HEYREACH_API_KEY"
]
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| YOUR_MCP_SERVER_URL | Endpoint or connection string the server talks to. | Yes |
| YOUR_HEYREACH_API_KEY | Credential the server authenticates with. | Yes |
| YOUR_API_KEY | Credential the server authenticates with. | Yes |
| CUSTOM_URL | Endpoint or connection string the server talks to. | Yes |
| HEYREACH_API_KEY | Credential the server authenticates with. | Yes |
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.
Inbox intelligence — search, read, draft and send Gmail through your assistant with OAuth auto-setup.
Read and write Jira, Confluence, Bitbucket, JSM and Compass from your AI client — with your own permissions.
Read and send Telegram messages through your assistant — chats, channels and history via the client API.
Enables Discord bot integration with Model Context Protocol (MCP) compatible applications like Claude Desktop.
Exposes REST APIs defined by OpenAPI specifications as Model Context Protocol (MCP) tools, facilitating seamless integration into MCP-based workflows.