Xtracticle

What Xtracticle MCP server does

The Xtracticle MCP server gives AI assistants a read-only way to retrieve public content from X, formerly Twitter. Its main MCP tool is read_x_post, exposed through the /mcp endpoint. The service is intended for posts, self-authored threads, and X Articles, converting retrieved content into Markdown that an agent can inspect or reuse.

X Articles can include article text, headings, inline images, videos, captions, and embedded posts. For threads, the service can assemble the author’s self-thread while excluding replies from other users. Individual posts may include text formatting, line breaks, media, and quoted posts. The broader application also supports Markdown and plain-text output through its HTTP API.

How it works

The Xtracticle MCP server uses Streamable HTTP rather than a local stdio process. Clients send MCP requests to POST /mcp; the endpoint is stateless. The application retrieves public X data through the FxTwitter API, using a v2 thread endpoint with a v1 fallback, then shared conversion code turns posts and articles into Markdown and related metadata.

The public API exposes separate routes for a single post, a thread, and Markdown output. Those routes are GET /api/tweet/:id, GET /api/thread/:id, and GET /api/markdown/:id. API and MCP responses are cached at the edge for five minutes, so callers should avoid unnecessary repeated requests.

Setup and configuration

For a hosted client connection, configure the MCP client to use the Xtracticle endpoint at https://xtracticle.com/mcp. The README describes the endpoint as requiring no authentication, and the deployment uses no environment variables.

To run the project locally, clone the repository, install dependencies with npm install, and start the development server with npm run dev. The local application runs at http://localhost:5173; its API is served by the same handler used by the Worker. npm run preview:worker runs the built Worker with Wrangler for a closer production-style test.

The Xtracticle MCP server is deployed with Cloudflare Workers and Static Assets. Production deployment is configured to run npm run build followed by npx wrangler deploy.

Tools and capabilities

• Read a public X post through the read_x_post MCP tool.
• Retrieve self-threads from a post reference, including when the reference points to the first, middle, or final post.
• Convert X Articles and posts into Markdown for downstream agent processing.
• Preserve supported content such as headings, emphasis, links, lists, quotes, code, images, video thumbnails, and quoted posts.
• Use public X URL forms and other supported post references handled by the application, including bare IDs and several alternative front-end URL formats.

Limitations and notes

The Xtracticle MCP server is read-only and does not provide authenticated access to private, protected, or account-specific X data. Thread assembly is limited to a user’s own self-thread; replies written by other people are excluded.

The MCP interface is documented with one tool, read_x_post. The available material does not document additional MCP tools, write operations, authentication options, or configurable environment variables. Because the endpoint is stateless and cached, clients should treat it as a retrieval service rather than a persistent conversation or storage layer.

The underlying content depends on public X availability and the FxTwitter API. Posts that are deleted, inaccessible, or unavailable through that source may not be retrievable.