twitterapi-docs-mcp
# twitterapi-docs-mcp
> **This package has been renamed to [`twitterapi-io-mcp`](https://www.npmjs.com/package/twitterapi-io-mcp).**
> `twitterapi-docs-mcp` is a compatibility wrapper that delegates to `twitterapi-io-mcp`. It still works, but future updates and support will only be available on the new package.
## Migration guide
Switching takes less than a minute. Update the package name in your MCP client config:
### Claude Code
```bash
# Remove old server and add new one
claude mcp remove twitterapi-docs-mcp
claude mcp add twitterapi-io-mcp -- npx -y twitterapi-io-mcp
```
### Claude Desktop
Edit `claude_desktop_config.json`:
```jsonc
{
"mcpServers": {
// Replace this:
// "twitterapi-docs-mcp": { "command": "npx", "args": ["-y", "twitterapi-docs-mcp"] }
// With this:
"twitterapi-io-mcp": {
"command": "npx",
"args": ["-y", "twitterapi-io-mcp"]
}
}
}
```
Config file location:
- **macOS**: `~/Library/Application Support/Claude/claude_desktop_config.json`
- **Windows**: `%APPDATA%\Claude\claude_desktop_config.json`
- **Linux**: `~/.config/Claude/claude_desktop_config.json`
### Cursor
Edit `.cursor/mcp.json` in your project root (or global config):
```jsonc
{
"mcpServers": {
"twitterapi-io-mcp": {
"command": "npx",
"args": ["-y", "twitterapi-io-mcp"]
}
}
}
```
### VS Code (Copilot)
Edit `.vscode/mcp.json` in your project root:
```jsonc
{
"servers": {
"twitterapi-io-mcp": {
"command": "npx",
"args": ["-y", "twitterapi-io-mcp"]
}
}
}
```
### Windsurf
Edit `~/.codeium/windsurf/mcp_config.json`:
```jsonc
{
"mcpServers": {
"twitterapi-io-mcp": {
"command": "npx",
"args": ["-y", "twitterapi-io-mcp"]
}
}
}
```
## Why migrate?
- **Future updates** will only be published to `twitterapi-io-mcp`
- **Direct support** via [GitHub Issues](https://github.com/dorukardahan/twitterapi-io-mcp/issues)
- **No wrapper overhead** - runs the server directly instead of delegating
## Legacy usage (still works)
```bash
npx -y twitterapi-docs-mcp
```
This wrapper prints a deprecation notice to stderr and delegates to `twitterapi-io-mcp`.
TDQS
Scored across 6 tools
Each tool has a clearly distinct purpose: get_twitterapi_auth handles authentication setup, get_twitterapi_endpoint provides specific endpoint details, get_twitterapi_guide covers conceptual topics, get_twitterapi_pricing focuses on costs and limits, list_twitterapi_endpoints offers a categorized overview, and search_twitterapi_docs enables cross-documentation search. There is no overlap in functionality, making tool selection straightforward for an agent.
All tool names follow a consistent snake_case pattern with a clear verb_noun structure (e.g., get_twitterapi_auth, list_twitterapi_endpoints, search_twitterapi_docs). The naming is predictable and uniform across all six tools, enhancing readability and usability.
With 6 tools, the server is well-scoped for its purpose of providing documentation access for TwitterAPI.io. Each tool serves a unique and necessary function, from authentication and endpoint details to guides, pricing, listing, and search, covering the domain comprehensively without being overwhelming.
The tool set offers complete coverage for accessing TwitterAPI.io documentation, including authentication, specific endpoints, conceptual guides, pricing, endpoint listings, and search capabilities. There are no obvious gaps; agents can retrieve all necessary information without dead ends, supporting a full range of documentation queries.