Usage instructions
Core usage
xbird is a set of Twitter/X integration tools for AI Agents. It provides 34 fine-grained tools through the MCP (Model Context Protocol) protocol, covering the complete life cycle of social media operations. Users need to passnpx @checkra1n/xbirdStart the local MCP server and configure the Twitter authentication cookie (auth_token, ct0) and optional wallet private key to enable x402 micropayments. The tools are divided into six categories by function: Read ($0.001/time) is used to obtain tweets, timelines, and user information; Search ($0.005/time) supports advanced search syntax; Bulk ($0.01/time) obtains user tweets in batches , watch list, etc.; Write ($0.01/time) performs interactive operations such as posting, replying, liking, and forwarding; Profile ($0.01/time) manages personal information; Media ($0.05/time) handles image and video uploads. Typical workflow includes: first callget_userParse the handle to obtain the numeric userId, and then use it for batch tools; the media must firstupload_mediaGet the mediaId and append it to the tweet.
Significant advantages
The pricing is transparent and billed by call, and the cost of low-frequency use is controllable; the tool granularity is extremely fine, and the Agent can be accurately combined to implement complex automation strategies; it supports advanced functions such as thread publishing, advanced search operators (from:/to:/since:/filter:media), and paging cursors; local operation is combined with residential IP to reduce the probability of platform risk control; the x402 payment protocol implements a pay-as-you-go model without subscription.
Potential Disadvantages and Limitations
Security architecture risks: The core logic is encapsulated in a closed-source npm package and cannot be audited locally;Credentials exposed: Sensitive cookies need to be manually extracted from the browser DevTools, which is cumbersome and error-prone;identity coupling: The Bulk tool mandates a numeric userId, adding an API round trip;payment threshold: The cost of high-frequency calls is accumulated, and there is no clear explanation of the free quota;platform dependency: Fully bound to Twitter/X private API, there is a risk of failure at any time;functional boundaries: Advanced functions such as private messages, spaces, and communities are not supported.
Suitable target group
Social media automation developers, AI Agent researchers, data analysts in brand operations teams, research institutions that need to collect public tweets in batches, and Twitter Bot prototype verifiers. It is especially suitable for individual developers or small teams who already have Twitter development experience, can accept the micropayment model, and have basic security awareness.
Risks of use
Account security: Cookie leakage can cause the account to be completely out of control, so it is recommended to use a dedicated alt account;financial risk: After the wallet private key is configured, there is a possibility of USDC being stolen and the balance needs to be controlled;Compliance risk: Automated interactions may trigger Twitter’s anti-spam policy and lead to account suspension;supply chain risk: Remote npm package updates may introduce unaudited code;performance risk: The local MCP server runs as a single point, without high availability guarantee;privacy risk: All operational data is transferred through a third-party server, and there is a man-in-the-middle attack surface.