MCP server & API

Live X data in Claude, Cursor or your own code (Pro).

The Futurepost MCP server puts live 𝕏 data into AI tools that speak the Model Context Protocol, like Claude, Cursor and ChatGPT's developer mode. Ask “what did @jack post this week?” or “who quoted this tweet?” and the assistant reads 𝕏 for you. The same key also opens a REST API.

The MCP server and API are part of Pro. A key stops working if the subscription ends.

In Claude (on the web, desktop or phone), open Settings → Connectors → Add custom connector, name it Futurepost and paste:

https://api.futurepost.ai/v1/mcp

Claude sends you to Futurepost to sign in with 𝕏 and press Allow. That's all: the connector shows up in Claude's tools menu. It appears under Connected apps in Settings → API & MCP, where you can disconnect it. Other apps that support MCP sign-in, such as ChatGPT's connectors, work the same way.

Other clients: make a key

Open Settings → API & MCP and press New key. Copy it straight away: it is shown only once. You can hold three keys and revoke any of them at any time.

Connect your client

The server URL is https://api.futurepost.ai/v1/mcp. Send your key as Authorization: Bearer <key>. The settings page shows each snippet with your key already filled in.

Claude Code

claude mcp add --transport http futurepost https://api.futurepost.ai/v1/mcp \
  --header "Authorization: Bearer YOUR_API_KEY"

Cursor

In ~/.cursor/mcp.json:

{
  "mcpServers": {
    "futurepost": {
      "url": "https://api.futurepost.ai/v1/mcp",
      "headers": { "Authorization": "Bearer YOUR_API_KEY" }
    }
  }
}

Claude Desktop

In claude_desktop_config.json (Settings → Developer → Edit Config), then restart Claude:

{
  "mcpServers": {
    "futurepost": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://api.futurepost.ai/v1/mcp",
               "--header", "Authorization: Bearer YOUR_API_KEY"]
    }
  }
}

What it can read

get_user, get_users: profiles by handle or id, up to 100 at once
get_user_tweets: an account's latest tweets, with or without replies
get_tweet, get_tweets: a tweet with its replies, or up to 20 tweets by id or link
search: 𝕏 search, with operators like from:, min_faves: and since:
get_followers, get_following: profiles, a page at a time
get_quotes, get_retweeters: who quoted or retweeted a tweet
get_friendship: whether two accounts follow each other
get_about_account: the country an account is based in, and its username changes
get_list: an 𝕏 list's details, tweets, members or followers

Everything is read only: the server never posts, follows or likes.

Limits

Each key (and each connected app) allows 30 reads a minute and 2,000 a day (the day resets at midnight UTC). A tool call is one read, or two when you give a handle where 𝕏 needs an id. Past a limit the tool answers with how long to wait. The settings page shows each key's reads today and this week.

The REST API

The same key works at https://api.futurepost.ai/v1/x, which follows TweetAPI's routes, so a TweetAPI client only needs its base URL changed:

curl "https://api.futurepost.ai/v1/x/user/tweets?userId=12" \
  -H "X-API-Key: YOUR_API_KEY"

GET /v1/x lists every route.

Still stuck? Email us at support@futurepost.ai or DM @futurepost on 𝕏, we usually reply within a day.

Claude: sign in, no key