The Twitter / X API for developers. Read and write X data over a plain REST API and an MCP server, billed per request. No X developer account, application, or approval process.
Get an API key (free $0.50 in credits, no card) · Docs · Pricing · MCP server
- Read tweets, advanced search, profiles, timelines, followers and following, likes, mentions, threads, replies, retweeters, and list members.
- Write as an authenticated account: post, reply, quote, like, retweet, bookmark, follow, and send DMs.
- Search with native X operators (
from:,min_faves:,since:,filter:links). - Call it in any language over REST, or drop the MCP server into Claude, Cursor, Windsurf, or VS Code and let your agent call X directly.
40 tools in all: 29 reads and 11 write actions, each mapped to a REST endpoint at https://api.twitterapis.com.
| Resource | Link |
|---|---|
| Sign up (free credits, no card) | https://www.twitterapis.com/signup |
| REST documentation | https://www.twitterapis.com/docs |
| Pricing | https://www.twitterapis.com/pricing |
| MCP server | https://github.com/TwitterAPIs/twitterapis-mcp |
| Cost calculator | https://www.twitterapis.com/twitter-api-cost-calculator |
| Rate limits | https://www.twitterapis.com/twitter-api-rate-limits |
| Alternatives compared | https://www.twitterapis.com/twitter-api-alternatives |
Do I need an X developer account? No. Sign up at twitterapis.com and get an API key. There is no application or approval step.
Is there a free tier? Every new key starts with $0.50 in credits and no card is required. After that you pay per request.
Which MCP clients work? Claude Desktop, Cursor, Windsurf, and VS Code (Copilot agent mode), or any client that speaks the Model Context Protocol.
Read-only, or can it post? Both. Reads need only an API key. Write actions (post, like, retweet, follow, DM) act as a linked X account.