Offline access to TwitterAPI.io docs for AI assistants. 52 endpoints, guides, pricing.
io.github.dorukardahan/twitterapi-docs-mcp is an MCP server that provides offline access to TwitterAPI.io documentation for AI assistants. The readme describes documentation coverage including endpoints, guides, and blog posts, with no API key requirement.
π οΈ Key Features
Offline TwitterAPI.io documentation via MCP
Coverage includes β67 active endpointsβ with full method/params/body
Includes 32 guides and 24 blog posts
βNo API key neededβ
π Use Cases
Reference TwitterAPI.io endpoint methods, parameters, and request bodies offline
Use included guides and blog posts to support AI-assisted development workflows
Build assistant tooling around Twitter/X API documentation via MCP
β‘ Developer Benefits
Direct endpoint and guide documentation availability through MCP
Includes structured endpoint details (method/params/body)
Works without requiring API keys
β οΈ Limitations
Content scope is limited to TwitterAPI.io documentation as described (offline docs, endpoints, guides, blog posts)
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.