Xbird

What checkra1neth/xbird MCP server does

checkra1neth/xbird MCP server connects AI agents to Twitter/X through the Model Context Protocol. The repository describes 247 tools covering account and post reading, search, timeline access, publishing, engagement, and media uploads. It is intended for local MCP use with clients such as Claude Code, Claude Desktop, Cursor, and Windsurf.

The MCP skill is one of three distributions in the repository. The other two are a REST API using x402 payments and an ACP integration for Virtuals Protocol. This writeup focuses on the local MCP server package, @checkra1n/xbird.

How it works

The MCP client starts @checkra1n/xbird as a local stdio process. With Bun, the server can automatically find Twitter/X browser cookies. With Node.js, the README documents a one-time login flow that saves the required auth_token and ct0 values locally.

Twitter/X requests are performed from the user's machine and residential IP. The remote xbird service verifies payments rather than acting as a general credential store or proxy for the Twitter API. A payment wallet is created automatically during the first run, and requests use x402 micropayments. The documented resource rates include separate charges for post reads, user reads, owned-content reads, post creation, interactions, and media uploads.

Setup and configuration

Install the package through Bun or npm. The recommended MCP command is:

bunx @checkra1n/xbird

For Node.js, use:

npx @checkra1n/xbird
npx @checkra1n/xbird login

The login command is used to save Twitter/X credentials locally. The README says to copy auth_token and ct0 from the x.com browser developer tools when using this route. Bun is described as requiring no manual login when browser cookies are available, while the Node.js path requires the one-time login command.

The repository also documents client-specific installation methods, including Claude Code’s MCP configuration command and direct MCP command configuration for Claude Desktop, Cursor, and Windsurf. No Twitter developer account, API key, or OAuth flow is listed as required for the MCP setup.

Tools and capabilities

The documented tool set supports tasks such as:

• Reading individual posts, replies, bookmarks, and home timelines
• Searching Twitter/X content
• Looking up users and followers
• Posting tweets and replying to posts
• Liking posts and following users
• Uploading media
• Managing other listed reading and engagement operations across the 247-tool catalog

The pricing examples show count-aware billing for some read operations. For example, searches and reply retrieval can use a requested count, with documented defaults and maximums for applicable resources. Creation and interaction operations are billed as individual resource actions.

Limitations and notes

checkra1neth/xbird MCP server is not described as a free, unlimited Twitter/X connection. Calls incur x402 micropayments, with listed resource rates starting at fractions of a cent per unit. A payment wallet is generated automatically, so an agent deployment must account for payment setup and balance management.

Browser-cookie access differs by runtime: Bun can auto-detect cookies, whereas Node.js requires manually completing the login process. The credentials and payment behavior described here apply to the local MCP path; the repository documents different security and transport models for its REST and ACP distributions.

The project is licensed under MIT. Its compatibility table names Claude Code, Claude Desktop, Cursor, and Windsurf, and also states that any MCP client can use the Bun or npm package command.