Twitterapi Docs Mcp
Give your agent offline TwitterAPI.io documentation—52 endpoints plus guides and pricing—while you implement X/Twitter integrations.
Overview
io.github.dorukardahan/twitterapi-docs-mcp is a MCP server for the Build phase that provides offline TwitterAPI.io docs covering 52 endpoints, guides, and pricing for your agent.
What is this MCP server?
- npm twitterapi-docs-mcp v1.0.3 stdio MCP—no live API key required for docs
- Offline corpus: 52 TwitterAPI.io endpoints with guides and pricing
- Reduces hallucinated endpoint paths while coding Twitter automations
- Pairs with TwitterAPI.io paid usage when you move from docs to live calls
- Documentation MCP, not a tweet posting or OAuth UI wizard
- Documents 52 TwitterAPI.io endpoints
- Package version 1.0.3 on npm
- Stdio transport; no required environment variables for doc access
Community signal: 5 GitHub stars.
What problem does it solve?
Agents guess wrong TwitterAPI.io paths and rate limits when you build integrations because public LLM training data is stale or incomplete.
Who is it for?
Developers wiring TwitterAPI.io into a side project who want citation-friendly endpoint and pricing answers inside Claude Code or Cursor.
Skip if: Builders who only need the official X API with no third-party proxy, or teams that want live tweet posting without reading docs first.
What do I get? / Deliverables
Installing the docs MCP gives your agent a grounded 52-endpoint reference so integration code and questions align with TwitterAPI.io before you spend credits on trial calls.
- Agent-queryable offline TwitterAPI.io docs including 52 endpoints
- Guide and pricing context for integration planning
- Reduced incorrect endpoint suggestions during implementation
Recommended MCP Servers
Journey fit
Third-party API doc lookup happens during Build when you wire social or distribution features into your app or agent. TwitterAPI.io is an external integration surface, which maps cleanly to the integrations subphase.
How it compares
Offline API documentation MCP, not a Twitter OAuth login skill or a scheduled posting workflow.
Common Questions / FAQ
Who is twitterapi-docs-mcp for?
It is for developers using TwitterAPI.io who want their coding agent to read accurate endpoint, guide, and pricing docs locally via MCP.
When should I use twitterapi-docs-mcp?
Use it during Build integrations whenever you design or debug calls against TwitterAPI.io before or alongside implementing live requests.
How do I add twitterapi-docs-mcp to my agent?
Add the npm stdio MCP server twitterapi-docs-mcp 1.0.3 to your client config; no environment variables are required for documentation access.