Remote MCP server

X (Twitter) MCP server for Claude, ChatGPT and Cursor.

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.

Server URLhttps://mcp.reachhunt.ai/mcp
  • No X API key
  • 87 tools
  • LinkedIn included
Claude
ReachHunt connected

Find everyone who retweeted my launch post and draft a DM campaign to the founders.

lead_lists_createList “Launch retweeters” created
lead_lists_start_import214 people imported from retweets
leads_search61 founders, 54 accept DMs
campaigns_create2-step DM campaign drafted from @acmecorp

Done. 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.

Claude wants to use campaigns_start

Sends DMs to 54 people from @acmecorp

AllowDeny
The basics

What an X MCP server does for your AI app.

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.

Tools

87 tools for X and LinkedIn, grouped the way you work.

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.

  • 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.

  • Lead lists

    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.

  • DM campaigns

    Create a DM sequence with follow-ups, then start, pause, resume or stop it, and follow every target and reply.

  • AI agents

    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.

  • Pipeline and CRM

    Set tags, statuses, notes, assignees and deal values on conversations and leads, add internal notes, and read your pipeline.

  • Accounts and limits

    See your connected accounts, how many DMs each can still send today, warm-up progress, credits and an activity summary.

Examples

Ask in plain words. The tools do the rest.

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.”

    Reads your inboxDrafts replies
  • “Import everyone who retweeted my launch post into a new list called Launch.”

    Builds a listImports retweets
  • “Look up @janedoe and check whether our @acmecorp account can DM them.”

    Looks up a profileChecks DMs are open
  • “Start a two-step DM campaign to the followers of @competitor, sent from all three of our X accounts.”

    Imports followersWrites the sequenceStarts the campaign
  • “Tag every conversation that mentions a demo as Hot and assign it to Sam.”

    Finds the chatsAdds a tagAssigns a teammate
  • “How many DMs can @acmecorp still send today, and how far along is its warm-up?”

    Checks today’s sendingShows warm-up
  • “Train an agent on our FAQ, test it with a pricing question, then put it on @acmecorp.”

    Trains an agentTests itPuts it live
  • “Schedule a friendly follow-up for every lead who went quiet last week.”

    Finds quiet leadsSchedules follow-ups
Setup

Connect in two minutes. No keys to copy.

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.

  • Claude

    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.

    Server URL
    https://mcp.reachhunt.ai/mcp
  • ChatGPT

    Open 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.

    MCP server URL
    https://mcp.reachhunt.ai/mcp
  • Cursor

    Add 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.

    mcp.json
    {
      "mcpServers": {
        "reachhunt": {
          "url": "https://mcp.reachhunt.ai/mcp"
        }
      }
    }
  • Claude Desktop config

    Apps that only run local servers can reach ReachHunt through mcp-remote. Add this to claude_desktop_config.json. It needs Node.js.

    claude_desktop_config.json
    {
      "mcpServers": {
        "reachhunt": {
          "command": "npx",
          "args": ["-y", "mcp-remote", "https://mcp.reachhunt.ai/mcp"]
        }
      }
    }
  • Claude Code

    Add the server from your terminal. Start Claude Code, type /mcp, choose reachhunt and select Authenticate.

    Terminal
    claude mcp add --transport http reachhunt https://mcp.reachhunt.ai/mcp
  • Codex CLI

    Add the server, then log in. Gemini CLI, VS Code with GitHub Copilot and Windsurf are covered in the docs.

    Terminal
    codex mcp add reachhunt --url https://mcp.reachhunt.ai/mcp
    codex mcp login reachhunt
Safety

Your AI app asks before anything goes out.

An AI app gets real power in your inbox, so the guardrails sit on the server, not in a prompt.

  • Sending tools are marked

    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.

  • Nothing can be deleted

    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.

  • Account safety built in

    Every X account keeps its safe daily pace and warm-up, whether a message comes from the app, a campaign, the API or MCP.

  • Sign-in, not keys

    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.

Compare

ReachHunt vs a typical open-source X MCP server.

ReachHunt MCP compared with a typical self-hosted X MCP server
ReachHunt MCPSelf-hosted X MCP
SetupPaste a URL and sign inClone, configure and run it
X developer app and API keysNot neededUsually required
HostingCloud, nothing to runYour machine or server
Read and send DMsDepends on your X API access
Lead lists from followers, retweets and likes
DM campaigns with follow-ups
AI agents that answer replies
Shared team inbox and pipeline
Per-account limits and warm-up
LinkedIn in the same server
FAQ

X MCP questions, answered.

Still have a question?

Book a demo

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.

Now live

Your next customer is one DM away.

Connect an account, build a list and switch on your AI agent — in about the time it took to read this page.

  • 14-day free trial
  • No card required
  • 2-minute setup