An MCP server for the "markitdown" library.
Until 2026-09-25 this record combined several servers published from one repository. The others now have records of their own: markitdown-mcp. Checks from before that date include them.
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"markitdown","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# MarkItDown-MCP [](https://pypi.org/project/markitdown-mcp/)  [](https://github.com/microsoft/autogen) The `markitdown-mcp` package provides a lightweight STDIO, Streamable HTTP, and SSE MCP server for calling MarkItDown. It exposes one tool: `convert_to_markdown(uri)`, where uri can be any `http:`, `https:`, `file:`, or `data:` URI. ## Installation To install the package, use pip: ```bash pip install markitdown-mcp ``` ## Usage To run the MCP server, using STDIO (default) use the following command: ```bash markitdown-mcp ``` To run the MCP server, using Streamable HTTP and SSE use the following command: ```bash markitdown-mcp --http --host 127.0.0.1 --port 3001 ``` ## Running in Docker To run `markitdown-mcp` in Docker, build the Docker image using the provided Dockerfile: ```bash docker build -t markitdown-mcp:latest . ``` And run it using: ```bash docker run -it --rm markitdown-mcp:latest ``` This will be sufficient for remote URIs. To access local files, you need to mount the local directory into the container. For example, if you want to access files in `/home/user/data`, you can run: ```bash docker run -it --rm -v /home/user/data:/workdir markitdown-mcp:latest ``` Once mounted, all files under data will be accessible under `/workdir` in the container. For example, if you have a file `example.txt` in `/home/user/data`, it will be accessible in the container at `/workdir/example.txt`. ## Accessing from Claude Desktop It is recommended to use the Docker image when running the MCP server for Claude Desktop. Follow [these instructions](https://modelcontextprotocol.io/quickstart/user#for-claude-desktop-users) to access Claude's `claude_desktop_config.json` file. Edit it to include the following JSON entry: ```json { "mcpServers": { …
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.