Give any Model Context Protocol client — Claude Desktop, Claude Code, custom agent runtimes — the ability to read X articles, threads, and tweets as clean Markdown, mid-conversation.
Model Context Protocol lets a model invoke external tools without you writing glue code in the chat. With an MCP server registered, Claude Desktop can recognise an X URL in your message and read it as part of its reply — no paste, no manual conversion. The xmd MCP server is the bridge between MCP clients and X content.
This is the same primitive other MCP servers expose — file system access, GitHub issues, database queries — but scoped to "fetch and parse X". The model gets a Markdown string back; you get answers that actually reflect what was posted.
The web converter is the only shipped surface today. The xmd MCP server is in development and ships next.
Add the xmd server to mcp_settings.json alongside your other MCP servers. Restart Claude Desktop, mention an X URL in a chat, and Claude calls into xmd to read it. Same flow as filesystem or GitHub MCP servers — different content source.
Register with claude mcp add, then any agent you run inside Claude Code has access to the X reading tool. Useful for agents that triage, summarise, or fact-check X content as part of a longer workflow.
MCP is an open spec. Any host that implements the protocol — custom agent runtimes, IDE plugins, chat UIs — can register the xmd server. The shipping transport details (stdio, HTTP) will be documented at launch.
The exact tool surface will be finalised at ship. The shape is straightforward — a tool that takes an X URL and returns Markdown, plus a resource handler for cached recent conversions so models can reference past lookups by reference instead of re-fetching.
Use the web converter directly. Paste an X URL, copy the Markdown, paste into Claude Desktop or Claude Code. Same Markdown your model will get from MCP — just one extra copy-paste hop.
Model Context Protocol is Anthropic's open standard for letting LLMs call out to external tools. An MCP server exposes named tools and resources; an MCP client (like Claude Desktop) discovers them and lets the model invoke them mid-conversation. xmd's MCP server lets Claude read X URLs directly, without you copy-pasting Markdown into the chat.
It is on the waitlist. The web converter is shipped today; the MCP server is the next surface to ship. Join the MCP Server waitlist on this page to get notified.
Yes. Claude Desktop is the primary MCP host today. Once the xmd MCP server ships, you'll add it to your Claude Desktop config (mcp_settings.json) and Claude can read X URLs the moment you mention one in a chat.
Yes. Claude Code supports MCP servers via the claude mcp add command. You'll be able to register the xmd server and any agent you run in Claude Code can read X URLs as part of its work.
Yes. The MCP spec is open, and a growing list of clients implement it — IDEs, custom agent runtimes, and chat UIs. Anything that speaks MCP can use the xmd server when it ships.
Want first access?