Twitterapi IO MCP

What twitterapi-io-mcp MCP server does

The twitterapi-io-mcp MCP server exposes a local reference library for TwitterAPI.io through MCP. It is intended for assistants that need to answer implementation questions, inspect endpoint requirements, or locate platform guidance. The bundled material covers current v2 endpoints, guides, and blog posts rather than making requests to TwitterAPI.io on the user’s behalf.

The documentation snapshot described by the project includes 67 active endpoints, 32 guide pages, and 24 blog posts. Endpoint records include HTTP methods, body or query parameters, cURL examples, and response schemas. The endpoint collection includes user, tweet, action, community, list, profile, webhook, stream, authentication, direct-message, account, and other categories.

How it works

An MCP-compatible client starts the package as a local Node.js process, typically through npx. The assistant then calls documentation tools over MCP and receives content from the locally bundled dataset. Since the server is documentation-only, it does not require a TwitterAPI.io API key and does not provide live API execution.

Use search_twitterapi_docs to find relevant material with full-text, fuzzy, and typo-tolerant matching. Once an endpoint is identified, get_twitterapi_endpoint returns its documented parameters, examples, and response structure. Category browsing is available through list_twitterapi_endpoints, while guides and individual pages can be retrieved with get_twitterapi_guide and get_twitterapi_url.

Setup and configuration

The package requires Node.js 18.18.0 or newer. Claude Code can add it with an MCP command that runs npx -y twitterapi-io-mcp; Claude Desktop, Cursor, VS Code, and Windsurf use equivalent stdio configuration entries with npx as the command. The repository also documents running it from Docker or from a local checkout after installing dependencies.

TWITTERAPI_MCP_DISK_CACHE controls disk caching. Caching is enabled by default, and setting this variable to 0 disables it. No API credential variable is required to start or use the documentation server.

Tools and capabilities

The twitterapi-io-mcp MCP server provides seven documented tools:

• search_twitterapi_docs searches endpoint documentation, guides, and posts.
• get_twitterapi_endpoint retrieves detailed information for a named endpoint.
• list_twitterapi_endpoints lists endpoints, with optional category filtering.
• get_twitterapi_guide returns named guides such as pricing, authentication, rate limits, webhooks, and streaming material.
• get_twitterapi_url loads content using a URL path or page key.
• get_twitterapi_pricing returns a focused pricing reference.
• get_twitterapi_auth returns a focused authentication reference.

The included endpoint set contains current v2 entries and removes deprecated v1 entries. It also documents write operations and related fields such as login_cookies, proxy, and request-body parameters where applicable. The project notes that TwitterAPI.io search now uses since_time and until_time with Unix timestamps instead of the disabled since: and until: operators.

Limitations and notes

This package is a documentation snapshot, not a live Twitter client. It cannot perform TwitterAPI.io calls, inspect account data, or replace credentials needed by an application that uses the actual API. Information is limited to the material bundled with the installed package, so changes made by TwitterAPI.io after that snapshot may require a newer package release.

The project is an independent community effort and states that it is not affiliated with TwitterAPI.io. If the first npx launch stalls, the documented alternatives are using the @latest package tag or installing the package globally. Client configuration changes may require restarting the MCP client before its tools appear.