Filesystem vs Zspace Cli
A side-by-side look at the Filesystem and Zspace Cli MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Filesystem for file systems work as a local process; choose Zspace Cli 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 Filesystem when
- You need dedicated capabilities in the File Systems domain.
- You prefer a local stdio subprocess transport.
- You want tools like
view, create, str_replace.
Choose Zspace Cli when
- You need dedicated capabilities in the File Systems domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
ZS_CONFIG_DIR.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | File Systems | File Systems |
| Quality signal | 52/100 · Good | 44/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | ZS_CONFIG_DIR |
| Verified owner | Community listing | Community listing |
| GitHub stars | 3 | 27 |
| Directory activity | 2 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 4 | Not listed |
| Full listing | View Filesystem | View Zspace Cli |
Tools & capabilities
Filesystem tools 4
viewRead file contents or list directory (with line numbers)createCreate or overwrite a filestr_replaceReplace an exact string in a fileinsertInsert text at a specific line
Zspace Cli 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.
Filesystem
{
"mcpServers": {
"filesystem-2": {
"command": "npx",
"args": [
"-y",
"filesystem-mcp"
]
}
}
}
Zspace Cli
{
"mcpServers": {
"zspace-cli": {
"command": "uvx",
"args": [
"zspace-cli"
],
"env": {
"ZS_CONFIG_DIR": "YOUR_ZS_CONFIG_DIR_HERE"
}
}
}
}
Frequently asked questions
Filesystem is categorized under File Systems and uses a local stdio subprocess. Zspace Cli belongs to File Systems and uses a local stdio subprocess. Pick Filesystem for file systems work and Zspace Cli 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.
Filesystem has no declared pricing — check the project's own site. Zspace Cli 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 filesystem-2 and zspace-cli as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Filesystem has a quality signal of 52/100 (Good) with 2 views, 0 installs and 3 GitHub stars. Zspace Cli has 44/100 (Fair) with 1 views, 0 installs and 27 GitHub stars.