MCP Upload vs Markitdown
A side-by-side look at the MCP Upload and Markitdown 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 MCP Upload for file systems work as a local process; choose Markitdown 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 MCP Upload when
- You need dedicated capabilities in the File Systems domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
OBJEKT_API_KEY. - You want tools like
upload_file, upload_from_sandbox, get_file.
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.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | Markitdown | |
|---|---|---|
| Category | File Systems | File Systems |
| Quality signal | 45/100 · Fair | 67/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | OBJEKT_API_KEY | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 191,245 |
| Directory activity | 1 views 0 installs 0 upvotes | 6 views 0 installs 0 upvotes |
| Tools | 4 | 1 |
| Full listing | View MCP Upload | View Markitdown |
Tools & capabilities
MCP Upload tools 4
upload_fileUpload by host path or inline contentupload_from_sandboxReturns curl command for sandbox uploadsget_fileGet file metadata and permalinkget_pricingCurrent storage tier pricing
Markitdown tools 1
convert_to_markdownConvert a resource described by an http:, https:, file: or data: URI to markdown
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.
MCP Upload
{
"mcpServers": {
"mcp-upload": {
"command": "npx",
"args": [
"-y",
"@objekt.sh/mcp-upload"
],
"env": {
"OBJEKT_API_KEY": "YOUR_OBJEKT_API_KEY_HERE"
}
}
}
}
Markitdown
{
"mcpServers": {
"microsoft-markitdown": {
"command": "uvx",
"args": [
"markitdown-ocr"
]
}
}
}
Frequently asked questions
MCP Upload is categorized under File Systems and uses a local stdio subprocess. Markitdown belongs to File Systems and uses a local stdio subprocess. Pick MCP Upload for file systems work and Markitdown 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.
MCP Upload has no declared pricing — check the project's own site. Markitdown is listed as free. Auth: no auth required. 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 mcp-upload and microsoft-markitdown as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, MCP Upload has a quality signal of 45/100 (Fair) with 1 views, 0 installs and 0 GitHub stars. Markitdown has 67/100 (Great) with 6 views, 0 installs and 191,245 GitHub stars.