Offline access to TwitterAPI.io docs for AI assistants. 54 endpoints, 19 pages, 21 blog posts.
If you already use Twitterapi, the twitterapi mcp server is the piece that lets your assistant work with it directly. Offline access to TwitterAPI.io docs for AI assistants. 54 endpoints, 19 pages, 21 blog posts.
An MCP server that gives Claude, Cursor, VS Code Copilot, and other AI assistants instant, offline access to TwitterAPI.io documentation.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
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 serverThe server ships on npm as twitterapi-io-mcp, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.
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.
This entry was verified against Twitterapi's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| 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-io": {
"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.