Markitdown vs Putput MCP
A side-by-side look at the Markitdown and Putput MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
MarkitdownFile Systems · Local subprocess (stdio)MCP tool access to MarkItDown -- a library that converts many file formats (local or remote) to Markdown for LLM consumption.67GreatAuth: no auth requiredVerdict: choose Markitdown for file systems work as a local process; choose Putput MCP for file systems as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Markitdown when
- You need dedicated capabilities in the File Systems domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
convert_to_markdown.
Choose Putput MCP when
- You need dedicated capabilities in the File Systems domain.
- You prefer a local stdio subprocess transport.
- You want tools like
upload_file, list_files, delete_file.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | Markitdown | |
|---|---|---|
| Category | File Systems | File Systems |
| Quality signal | 67/100 · Great | 49/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | No auth required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 191,245 | 1 |
| Directory activity | 6 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 1 | 4 |
| Full listing | View Markitdown | View Putput MCP |
Tools & capabilities
Markitdown tools 1
convert_to_markdownConvert a resource described by an http:, https:, file: or data: URI to markdown
Putput MCP tools 4
upload_fileUpload a file from a URL to PutPut and get a CDN link backlist_filesList uploaded files with optional prefix filter and paginationdelete_fileDelete a file by IDget_file_infoGet file details, stats, and download URL
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Markitdown
{
"mcpServers": {
"microsoft-markitdown": {
"command": "uvx",
"args": [
"markitdown-ocr"
]
}
}
}
Putput MCP
{
"mcpServers": {
"putput-mcp": {
"command": "npx",
"args": [
"@putput/mcp"
]
}
}
}
Frequently asked questions
Markitdown is categorized under File Systems and uses a local stdio subprocess. Putput MCP belongs to File Systems and uses a local stdio subprocess. Pick Markitdown for file systems work and Putput MCP for file systems.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Markitdown is listed as free. Auth: no auth required. Putput MCP has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add microsoft-markitdown and putput-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Markitdown has a quality signal of 67/100 (Great) with 6 views, 0 installs and 191,245 GitHub stars. Putput MCP has 49/100 (Fair) with 1 views, 0 installs and 1 GitHub stars.