Twitterapi Io Mcp
Give Claude or Cursor offline TwitterAPI.io reference while you wire X/Twitter posting, search, or webhooks into a product.
Overview
TwitterAPI.io MCP is a MCP server for the Build phase that exposes offline TwitterAPI.io documentation (67 endpoints, 32 pages, 24 blog posts) to coding agents over stdio.
What is this MCP server?
- Offline mirror of TwitterAPI.io documentation for MCP clients—no tab-hopping while coding
- Coverage cited in registry: 67 API endpoints, 32 doc pages, and 24 blog posts
- npm package twitterapi-io-mcp v1.5.9 with stdio transport for local Claude Code / Cursor configs
- Lets assistants answer auth, rate limits, and endpoint shapes from indexed docs instead of hallucinating paths
- 67 documented API endpoints in the offline corpus
- 32 documentation pages mirrored
- 24 blog posts included
Community signal: 5 GitHub stars.
What problem does it solve?
Agents guess X API paths and parameters when TwitterAPI.io docs are not in context, wasting tokens and producing broken integration code.
Who is it for?
Indie builders shipping Twitter/X automation, social dashboards, or growth bots on top of TwitterAPI.io inside Claude Code or Cursor.
Skip if: Teams that only need to post tweets once with no custom code, or anyone expecting live Twitter API execution without writing their own HTTP layer.
What do I get? / Deliverables
Your agent can ground answers in the mirrored TwitterAPI.io catalog while you scaffold clients, webhooks, and error handling in your repo.
- Context-grounded answers about TwitterAPI.io endpoints and guides during coding
- Faster scaffolding of TwitterAPI.io HTTP clients with fewer invented routes
Recommended MCP Servers
Journey fit
Canonical shelf is Build because the server exists to help you implement TwitterAPI.io integrations, not to run marketing or ops dashboards by itself. Agent-tooling fits a bundled doc corpus (endpoints, pages, blog) exposed to coding agents during implementation.
How it compares
Offline documentation MCP for TwitterAPI.io—not a hosted Twitter proxy or a single Claude skill.
Common Questions / FAQ
Who is TwitterAPI.io MCP for?
Solo developers and agent users who integrate TwitterAPI.io and want indexed docs available inside Claude Code, Cursor, or other MCP clients.
When should I use TwitterAPI.io MCP?
Use it during Build when you are mapping endpoints, auth, and payloads for X/Twitter features and want the assistant to read the bundled 67-endpoint doc set.
How do I add TwitterAPI.io MCP to my agent?
Install the npm package twitterapi-io-mcp, add an MCP server entry with stdio transport pointing at that binary, restart the client, and grant doc lookup tools in your project.