A side-by-side look at the Ctxd and MCP Filesystem 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 MCP Filesystem Server for file systems. 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.
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.
No confirmed install command for MCP Filesystem Server yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
Ctxd is categorized under File Systems and uses a local stdio subprocess. MCP Filesystem Server belongs to File Systems and uses an install path we have not confirmed yet. Pick Ctxd for file systems work and MCP Filesystem 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. MCP Filesystem Server has no confirmed install command yet — follow its own setup instructions.
Ctxd is listed as free. Auth: no auth required. MCP Filesystem Server 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 ctxd and mark3labs-mcp-filesystem-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. MCP Filesystem Server has 49/100 (Fair) with 5 views, 0 installs and 692 GitHub stars.