AI agents read text. The world ships documents as PDFs, Word files and slide decks. t0md is the bridge — an MCP server that gives any agent a single tool for turning any document into clean Markdown.
Building an agent that does real work usually means handling documents the user already has — a contract, a research paper, a vendor spec. Most of those arrive as PDFs or Office files. Without a conversion tool, the agent stalls: it can't read the document, can't quote it, can't reason over it. With t0md plugged in over MCP, the agent acquires a `convert_to_markdown` tool that handles PDF, .docx, .pptx, HTML and JSON behind one interface. The agent doesn't need to know how each format works — it just hands the file path to t0md and gets Markdown back.
Register t0md as an MCP server in your agent runtime. Claude Code, Cursor, Windsurf, Hermes, OpenClaw and Continue.dev all support streamable-HTTP MCP — the same one-line add command works across them. For agents you're building yourself, point your MCP client library at `https://t0md.com/mcp`. The tool surface is small (one `convert_to_markdown` call), the model figures out when to use it on its own.
# Generic MCP client config (streamable-HTTP)
mcpServers:
- name: t0md
url: https://t0md.com/mcp
transport: streamable-http
tools:
include: [convert_to_markdown]Streamable-HTTP (the modern MCP transport). SSE is also exposed at /mcp/sse for clients that still need it. For stdio-only clients, there's a small bridge binary in the t0md-mcp repo.
MCP advertises a tool description and parameter schema. The model reads those on its own and picks the right tool when a request matches — no prompt engineering required. Optionally pin to convert_to_markdown via your client's tool allow-list.
Yes. t0md is open source; clone the repo, run `go build ./cmd/server`, point your agents at your instance via the T0MD_URL env var (for the stdio bridge) or the MCP server URL directly.