Skip to main content
Your coding agent can build on ReachHunt for you. Give it two MCP servers: one to work in your workspace, and one to search these docs. Every page is also available as plain markdown, so the agent reads the same docs you do.

What your agent gets

Both servers use Streamable HTTP over HTTPS. You don’t run anything locally.

Connect your agent

Run these in your terminal:
Start Claude Code, type /mcp, choose reachhunt and select Authenticate. A ReachHunt page opens in your browser. Choose your workspace and select Connect.
For Claude, ChatGPT and other chat apps, follow MCP server.

Docs built for agents

Try this prompt

Paste this into your agent after you connect both servers:
The agent looks up the event payload and the webhook guide in the docs, writes the handler, and checks the secret header with a constant-time comparison.

Tell your agent

These are the details agents most often get wrong:
  • Every response has the same envelope. Read data when status is true, and error when it is false. See Response format.
  • Items carry a platform. It is x or linkedin. Many fields differ between the two.
  • Sending limits apply per account. The app, campaigns and the API share them. Check them with Get account limits before you send in bulk. See Rate limits.
  • ReachHunt doesn’t sign webhooks. Add a secret header and compare it in constant time. See Receive webhooks.
The ReachHunt MCP server acts as the workspace owner and sends real messages from your connected accounts. Try new agent code on a test workspace first, and never commit an API key.

Next steps

MCP server

What the ReachHunt MCP server can do, and its limits.

Quickstart

Make your first API request.

Webhooks

Get events sent to your server as they happen.