A side-by-side look at the Ctxd and Filesystem MCP 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 Filesystem 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 Ctxd when
You need dedicated capabilities in the File Systems domain.
No tool names declared yet. Check the project README from the listing page.
Filesystem MCP 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.
Ctxd is categorized under File Systems and uses a local stdio subprocess. Filesystem MCP belongs to File Systems and uses a local stdio subprocess. Pick Ctxd for file systems work and Filesystem 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.
Ctxd is listed as free. Auth: no auth required. Filesystem MCP 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 lincolnburrows2017-filesystem-mcp 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. Filesystem MCP has 45/100 (Fair) with 2 views, 0 installs and 2 GitHub stars.