MCPRemote server · HTTP transport

Give your agent rich X data

Connect Claude, Cursor or any MCP client to twitterxapi. Your agent can search posts, read profiles, threads, lists, trends and communities with eight ready-made tools.

Get your API keyDashboard MCP docs

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

claude mcp add --transport http twitterxapi \
  https://twitterxapi.com/api/mcp \
  --header "Authorization: Bearer $TWITTERXAPI_KEY"

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

# TwitterXAPI MCP server

Remote HTTP MCP server for X data: profiles, posts, threads, followers, search, Lists, trends and communities.

- Endpoint: `https://twitterxapi.com/api/mcp`
- Header: `Authorization: Bearer <TWITTERXAPI_KEY>` (same key, balance and prices as the REST API)

## Client configuration

Replace `<TWITTERXAPI_KEY>` with the key from https://twitterxapi.com/dashboard/. Keep the file out of version control.

```json
{
  "mcpServers": {
    "twitterxapi": {
      "type": "http",
      "url": "https://twitterxapi.com/api/mcp",
      "headers": {
        "Authorization": "Bearer <TWITTERXAPI_KEY>"
      }
    }
  }
}
```

## Tools

| Tool | Reads | Arguments |
| --- | --- | --- |
| `search_x` | Search posts, accounts, or the posts behind a trend. | `query` (required), `kind`: posts (default) | users | trend, `cursor` |
| `get_x_user` | A profile by username or ID, or the account's About information. | `username` or `userId`, `kind`: profile (default) | about. About needs `username`. |
| `get_x_user_timeline` | One page of an account's posts, posts and replies, or media. | `username` (required), `kind`: posts (default) | posts_and_replies | media, `cursor` |
| `get_x_user_network` | One page of followers, verified followers, following, or subscriptions. | `userId` (required), `kind` (required): followers | verified_followers | following | subscriptions, `cursor` |
| `get_x_post` | A post, or one page of its replies, thread, or retweeters. | `tweetId` (required), `kind`: details (default) | replies | thread | retweeters, `cursor` |
| `get_x_list` | One page of a List's posts or members. | `listId` (required), `kind`: posts (default) | members, `cursor` |
| `get_x_trends` | One page of trends for a category. | `category` (default trending), `cursor` |
| `get_x_community` | Community information, or one page of its posts, members, or moderators. | `communityId` (required), `kind`: info (default) | posts | members | moderators, `cursor` |

Collection tools return one page per call. Pass `pagination.next_cursor` from the result as `cursor` for the next page and stop when `has_more` is false. Set a page budget for open-ended research, since every call is billed like a REST request.

## Results

- `content[0].text` is compact Contentful JSON.
- `structuredContent.data` is the Moderate form with IDs and cursors.
- Errors set `isError: true` with `structuredContent.data.error.code`.
- Raw responses and queued jobs are REST-only: https://twitterxapi.com/api/v1

Replace <TWITTERXAPI_KEY> with the key from your dashboard.

Get your API keyAdd the server to your clientAsk your agent about anything on X

🤖

Tools your agent can call

search_xSearch posts, accounts, or the posts behind a trend.

get_x_userA profile by username or ID, or the account's About information.

get_x_user_timelineOne page of an account's posts, posts and replies, or media.

get_x_user_networkOne page of followers, verified followers, following, or subscriptions.

get_x_postA post, or one page of its replies, thread, or retweeters.

get_x_listOne page of a List's posts or members.

get_x_trendsOne page of trends for a category.

get_x_communityCommunity information, or one page of its posts, members, or moderators.

Answers your agent can read

Each tool result includes Contentful text for the model to read and Moderate structured data for follow-up calls. Requests are billed per record, the same as the HTTP API.

Illustrative workflow, not a live response

Who are the most followed accounts replying to @marclou's latest post?

⚙get_x_user_timeline✓

⚙get_x_post · replies✓

I can compare the accounts in the returned replies by follower count, with links to each reply.

Connect your agent in a minute

Get API key