Ctxd vs Filekiwi MCP Server
A side-by-side look at the Ctxd and Filekiwi MCP Server MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Ctxd for file systems work as a local process; choose Filekiwi MCP Server 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 Ctxd 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.
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.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | File Systems | File Systems |
| Quality signal | 47/100 · Fair | 53/100 · Good |
| 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 | 63 | 6 |
| Directory activity | 1 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | Not listed | 1 |
| Full listing | View Ctxd | View Filekiwi MCP Server |
Tools & capabilities
Ctxd tools
No tool names declared yet. Check the project README from the listing page.
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.
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.
Ctxd
{
"mcpServers": {
"ctxd": {
"command": "uvx",
"args": [
"ctxd"
]
}
}
}
Filekiwi MCP Server
{
"mcpServers": {
"filekiwi-mcp-server": {
"command": "npx",
"args": [
"-y",
"@file-kiwi/filekiwi-mcp-server"
]
}
}
}
Frequently asked questions
Ctxd is categorized under File Systems and uses a local stdio subprocess. Filekiwi MCP Server belongs to File Systems and uses a local stdio subprocess. Pick Ctxd for file systems work and Filekiwi MCP Server 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.
Ctxd is listed as free. Auth: no auth required. Filekiwi MCP Server 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 ctxd and filekiwi-mcp-server as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Ctxd has a quality signal of 47/100 (Fair) with 1 views, 0 installs and 63 GitHub stars. Filekiwi MCP Server has 53/100 (Good) with 1 views, 0 installs and 6 GitHub stars.