Filekiwi MCP Server vs Markitdown
A side-by-side look at the Filekiwi MCP Server 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.59GoodAuth: no auth requiredVerdict: choose Filekiwi MCP Server 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 Filekiwi MCP Server when
- You need dedicated capabilities in the File Systems domain.
- You prefer a local stdio subprocess transport.
- You want tools like
upload_to_kiwi.
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.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | Markitdown | |
|---|---|---|
| Category | File Systems | File Systems |
| Quality signal | 53/100 · Good | 59/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 6 | 191,245 |
| Directory activity | 1 views 0 installs 0 upvotes | 6 views 0 installs 0 upvotes |
| Tools | 1 | Not listed |
| Full listing | View Filekiwi MCP Server | View Markitdown |
Tools & capabilities
Filekiwi MCP Server tools 1
upload_to_kiwiUpload files to file.kiwi and return the share URL. IMPORTANT: Only real file system paths work (e.g. C:\Users\username\Desktop\file.png). Paths like /mnt/user-data/uploads/ or /home/claude/ are virtual and will fail. Ask the user for the actual local file path on their computer.
Markitdown tools
No tool names declared yet. Check the project README from the listing page.
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.
Filekiwi MCP Server
{
"mcpServers": {
"filekiwi-mcp-server": {
"command": "npx",
"args": [
"-y",
"@file-kiwi/filekiwi-mcp-server"
]
}
}
}
Markitdown
{
"mcpServers": {
"microsoft-markitdown": {
"command": "uvx",
"args": [
"markitdown-mcp"
]
}
}
}
Frequently asked questions
Filekiwi MCP Server is categorized under File Systems and uses a local stdio subprocess. Markitdown belongs to File Systems and uses a local stdio subprocess. Pick Filekiwi MCP Server 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.
Filekiwi MCP Server 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 filekiwi-mcp-server and microsoft-markitdown as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Filekiwi MCP Server has a quality signal of 53/100 (Good) with 1 views, 0 installs and 6 GitHub stars. Markitdown has 59/100 (Good) with 6 views, 0 installs and 191,245 GitHub stars.