MCP server

Use X/Twitter data in your AI assistant

RelayX ships a Model Context Protocol (MCP) server: Claude, ChatGPT, Cursor and Claude Code call 29 read-only tools and answer with live X (Twitter) data — no glue code, billed per call.

See it work

You     › What has @nasa posted this week?

Claude  ● relayx · user_last_tweets(userName: "nasa")
          ⎿ 20 tweets · 260 credits

Here's what @nasa posted this week:
 · a launch-day update from the Cape
 · a new image from the Webb telescope
 · an ISS crew Q&A announcement

Illustrative — your assistant decides which tool to call and how to phrase the answer.

What you get

29 read-only tools over RelayX’s endpoints — user profiles, tweets, replies, quotes, retweeters, advanced search, followers and followings, lists, communities, Spaces and trends — plus thesearch and fetch tools ChatGPT’s connector expects. Ask a question; the assistant calls the right tool and reads back real data.

Connect it

Endpoint: https://api.relayxapi.com/mcp · full tool list, example prompts and troubleshooting in theMCP setup guide.

Claude Code

claude mcp add --transport http relayx https://api.relayxapi.com/mcp

Then run /mcp in Claude Code to sign in to RelayX (OAuth) and pick a key. Prefer to pass a key directly? Add --header "Authorization: Bearer YOUR_KEY" to the command.

Cursor

One-click install, or add it to ~/.cursor/mcp.json:

{
  "mcpServers": {
    "relayx": { "url": "https://api.relayxapi.com/mcp" }
  }
}

Add "headers": { "Authorization": "Bearer YOUR_KEY" } to use a key instead of OAuth.

Claude (claude.ai / Claude Desktop)

Settings → Connectors → Add custom connector, and paste the endpoint URL. Claude registers itself, opens the RelayX sign-in page, and you pick which API key it may spend (OAuth — no key pasted into the client).

ChatGPT

Enable developer mode, then add a connector with the endpoint URL and OAuth authentication. Deep research uses the search and fetch tools.

Billing

Each tool call spends credits from your account at the same per-item rates as the REST API — see pricing. No subscription; new keys include free trial credits. The MCP server is read-only (write actions are available over REST).

FAQ

What is the RelayX MCP server?

An MCP (Model Context Protocol) endpoint that exposes RelayX’s X (Twitter) data as 29 tools an AI assistant can call directly — look up profiles, fetch tweets, search — without you writing any API glue code.

Which assistants can use it?

Any MCP client: Claude (claude.ai and Claude Desktop) and ChatGPT via OAuth; Claude Code and Cursor via OAuth or an API-key header.

Do I paste my API key into the assistant?

Not with OAuth: the client opens a RelayX sign-in page and you choose which of your keys it may spend. With Claude Code or Cursor you can alternatively pass the key as an Authorization header.

How is it billed?

The same as the REST API: each tool call spends credits from your account at the same per-item rates. There is no subscription, and new keys include free trial credits. The MCP server is read-only.