Offline access to TwitterAPI.io docs for AI assistants. 52 endpoints, guides, pricing.
Twitterapi MCP server exists for a simple reason — assistants are far more useful when they can act on Twitterapi directly instead of describing what you should do. Offline access to TwitterAPI.io docs for AI assistants. 52 endpoints, guides, pricing.
An MCP server that gives Claude, Cursor, VS Code Copilot, and other AI assistants instant, offline access to TwitterAPI.io documentation.
Once Twitterapi is connected, these are the calls the assistant has available:
search_twitterapi_docs — Full-text search across all docs (fuzzy matching, typo-tolerant)get_twitterapi_endpoint — Get full endpoint documentation with params, examples, response schemalist_twitterapi_endpoints — List endpoints, optionally filtered by categoryget_twitterapi_guide — Get guide pages (pricing, auth, rate limits, webhooks, etc.)get_twitterapi_url — Fetch content by URL path or page keyget_twitterapi_pricing — Quick pricing overviewget_twitterapi_auth — Quick authentication guideCursor — The Cursor tool exposed by this serverWindsurf — The Windsurf tool exposed by this servertwitterapi-io-mcp on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.
Plenty of knowledge and memory servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Twitterapi's toolset — search_twitterapi_docs, get_twitterapi_endpoint, list_twitterapi_endpoints and 6 more — is a fair guide to whether it matches your workflow. It is maintained by dorukardahan; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| search_twitterapi_docs | Full-text search across all docs (fuzzy matching, typo-tolerant) |
| get_twitterapi_endpoint | Get full endpoint documentation with params, examples, response schema |
| list_twitterapi_endpoints | List endpoints, optionally filtered by category |
| get_twitterapi_guide | Get guide pages (pricing, auth, rate limits, webhooks, etc.) |
| get_twitterapi_url | Fetch content by URL path or page key |
| get_twitterapi_pricing | Quick pricing overview |
| get_twitterapi_auth | Quick authentication guide |
| Cursor | The Cursor tool exposed by this server. |
| Windsurf | The Windsurf tool exposed by this server. |
{
"mcpServers": {
"twitterapi-docs": {
"command": "npx",
"args": ["-y", "twitterapi-io-mcp"]
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
A knowledge graph your assistant keeps between sessions — entities, relations and observations that persist.
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Your workspace, on speaking terms with AI — search, read and write Notion pages and databases.
A structured scratchpad for hard problems — stepwise reasoning with revisions, branches and visible logic.
Symbol-level code navigation, refactoring and memory for coding agents — the IDE brain your assistant has been missing.
Chat with your second brain — search, read and write vault notes through the Local REST API.