Inbox and messages
List conversations and message requests, read threads, send and react to DMs, schedule a message for later, and close or reopen threads on any connected X account.
Sign in once and your AI app works in X through the accounts you already use. It reads your DMs, replies to leads, builds lead lists from followers and retweets, and runs DM campaigns. No X API key, no developer account, nothing to host.
https://mcp.reachhunt.ai/mcpFind everyone who retweeted my launch post and draft a DM campaign to the founders.
lead_lists_createList “Launch retweeters” createdlead_lists_start_import214 people imported from retweetsleads_search61 founders, 54 accept DMscampaigns_create2-step DM campaign drafted from @acmecorpDone. 54 founders from your launch retweets can get a DM. The campaign sends a short intro from @acmecorp, then one follow-up after 3 days if they don’t reply.
campaigns_startSends DMs to 54 people from @acmecorp
MCP (Model Context Protocol) is the open standard AI apps use to call outside tools. Claude, ChatGPT, Cursor, Claude Code, Codex and Gemini CLI all support it. An X MCP server gives your AI app tools for X, so instead of copying DMs into a chat, you ask in plain words and the app does the work.
Most X MCP servers on GitHub wrap the official X API. You create an X developer app, manage API keys and plan limits, and run the server on your own machine. ReachHunt works differently: the server runs in the cloud at mcp.reachhunt.ai, you sign in with your ReachHunt account, and every action goes through the X accounts connected to your workspace, inside the limits that keep them safe.
The same server covers LinkedIn, so one connection gives Claude or ChatGPT both networks, one inbox and one pipeline.
Each tool maps to one ReachHunt API operation. Tools that only read run straight away. Tools that reach real people are marked, so your AI app asks you first.
List conversations and message requests, read threads, send and react to DMs, schedule a message for later, and close or reopen threads on any connected X account.
Look up X profiles and whether they accept DMs, search people live on X, and import followers, following, retweets, comments, post likes, list members or chat contacts into a lead list.
Create a DM sequence with follow-ups, then start, pause, resume or stop it, and follow every target and reply.
Create and train an agent, test it, publish it, put it on one or all of your X accounts, and pause it when you want to take over.
Set tags, statuses, notes, assignees and deal values on conversations and leads, add internal notes, and read your pipeline.
See your connected accounts, how many DMs each can still send today, warm-up progress, credits and an activity summary.
Real requests your AI app can handle in ReachHunt, in plain words.
“Summarize my unread X DMs from today and draft replies to anyone asking about pricing.”
“Import everyone who retweeted my launch post into a new list called Launch.”
“Look up @janedoe and check whether our @acmecorp account can DM them.”
“Start a two-step DM campaign to the followers of @competitor, sent from all three of our X accounts.”
“Tag every conversation that mentions a demo as Hot and assign it to Sam.”
“How many DMs can @acmecorp still send today, and how far along is its warm-up?”
“Train an agent on our FAQ, test it with a pricing question, then put it on @acmecorp.”
“Schedule a friendly follow-up for every lead who went quiet last week.”
Paste the server URL, sign in to ReachHunt in the browser window that opens, and pick your workspace. You need full access to Developer in the workspace and an active plan.
On claude.ai or the desktop app, open Customize, then Connectors. Select + Add, then Add custom connector, name it ReachHunt and paste the URL. Select Connect, pick your workspace, then turn ReachHunt on from the + menu in a chat.
https://mcp.reachhunt.ai/mcpOpen Settings, then Apps, then Advanced settings, and turn on Developer mode. Back in Apps, select Create app, name it ReachHunt, paste the URL as the MCP server URL, choose OAuth and connect your workspace.
https://mcp.reachhunt.ai/mcpAdd ReachHunt to ~/.cursor/mcp.json, or .cursor/mcp.json inside one project. Then open Cursor Settings, then MCP, and select the sign-in button next to reachhunt.
{
"mcpServers": {
"reachhunt": {
"url": "https://mcp.reachhunt.ai/mcp"
}
}
}Apps that only run local servers can reach ReachHunt through mcp-remote. Add this to claude_desktop_config.json. It needs Node.js.
{
"mcpServers": {
"reachhunt": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://mcp.reachhunt.ai/mcp"]
}
}
}Add the server from your terminal. Start Claude Code, type /mcp, choose reachhunt and select Authenticate.
claude mcp add --transport http reachhunt https://mcp.reachhunt.ai/mcpAdd the server, then log in. Gemini CLI, VS Code with GitHub Copilot and Windsurf are covered in the docs.
codex mcp add reachhunt --url https://mcp.reachhunt.ai/mcp
codex mcp login reachhuntAn AI app gets real power in your inbox, so the guardrails sit on the server, not in a prompt.
Tools that reach real people, like sending a DM or starting a campaign, carry an open-world flag. Claude and ChatGPT show you the action and wait for your OK.
Your AI app can’t delete conversations, messages, lead lists, campaigns, agents, templates, tags or statuses. It can stop a campaign or cancel a scheduled message.
Every X account keeps its safe daily pace and warm-up, whether a message comes from the app, a campaign, the API or MCP.
You connect with OAuth and pick a workspace. ReachHunt creates an API key named after the app in that workspace, so you always see which apps have access.
A remote MCP server at https://mcp.reachhunt.ai/mcp that gives AI apps 87 tools for your ReachHunt workspace. On X, your AI app can read and send DMs, look up profiles, build lead lists, run DM campaigns and manage AI agents through the X accounts you connected.
Connect an account, build a list and switch on your AI agent — in about the time it took to read this page.