Offline access to TwitterAPI.io docs for AI assistants. 67 endpoints, 32 pages, 24 blog posts.
twitterapi-io-mcp (MCP) Server
The io.github.dorukardahan/twitterapi-io-mcp server provides offline access to TwitterAPI.io documentation for AI assistants via the Model Context Protocol (MCP). It is based on 67 active endpoints (including method/params/body), with 32 guides and 24 blog posts available for reference.
π οΈ Key Features
Offline TwitterAPI.io documentation access via MCP
67 active endpoints with full method/params/body details
32 guides
24 blog posts
No API key required (per readme excerpt)
π Use Cases
Reference TwitterAPI.io endpoint signatures and request inputs without network access
Use MCP-enabled tooling in Claude/AI assistant workflows for TwitterAPI.io lookups
Browse guides and blog posts to understand API usage
β‘ Developer Benefits
Offline documentation reduces dependency on external connectivity
Offline TwitterAPI.io documentation for Claude and AI assistants via MCP. 67 active endpoints (with full method/params/body), 32 guides, 24 blog posts. No API key needed.
All v2 write endpoints documented with login_cookies, proxy, and body params
All deprecated v1 endpoints removed β only current v2 endpoints remain
Zero API key required β everything is bundled locally
Unlike other Twitter MCP servers that proxy live API calls (and need your API key), this one ships a complete documentation snapshot. Your AI assistant reads it locally, instantly.
AI assistant calls an MCP tool (search, get endpoint, etc.)
Server searches the bundled documentation snapshot
Results return instantly with no network requests
Why I built this
I use TwitterAPI.io daily for my projects. Switching between my editor and their docs site got old fast. So I packaged the entire documentation into an MCP server. Now I ask Claude and get answers without leaving my terminal.
If you work with the Twitter/X API through TwitterAPI.io, this saves you the same context-switching. Install it, forget about it, and just ask.
Development
bash
git clone https://github.com/dorukardahan/twitterapi-io-mcp.git
cd twitterapi-io-mcp
npm install
npm test# Run tests (48 tests)
npm start # Start server locally
npm run scrape # Update docs snapshot from twitterapi.io
Not using MCP?
If your AI tool doesn't support MCP (like OpenClaw), use the skill version instead β a single markdown file with all 67 active endpoints:
π twitterapi-io-skill β works with OpenClaw, Claude, GPT, Gemini, and any LLM.