MCP SERVER

Give your agent direct access to public X data.

Connect with the same API key used for REST. MCP calls share your balance, pricing, account pool, and request history.

Add one HTTP server.

Paste this configuration into an MCP-compatible client, then replace the placeholder with your customer API key.

mcp.json

{
  "mcpServers": {
    "twitterxapi": {
      "type": "http",
      "url": "https://twitterxapi.com/api/mcp",
      "headers": {
        "Authorization": "Bearer tx_live_..."
      }
    }
  }
}

Tools your agent can call

search_x

Search public posts, accounts, and trend pages.

get_x_user

Read a profile by username or ID, including its About data.

get_x_user_timeline

Fetch an account's posts, replies, or media.

get_x_user_network

Page through followers, following, and subscriptions.

get_x_post

Read post details, replies, threads, and retweeters.

get_x_list

Fetch posts or members from a public list.

get_x_trends

Read category-based trend pages.

get_x_community

Read community information, posts, members, and moderators.

COLLECTIONS

One page at a time, with a cursor for the next.

Collection tools return one upstream page per call. Use the continuation cursor to chain requests without guessing where the next page begins.

Tool text uses compact Contentful JSON to keep model context small. structuredContent.data carries the Moderate form, including IDs and cursors, for reliable follow-up calls.

Raw X responses and queued exports stay on the REST API and are not exposed through MCP.