MCP Filesystem vs Wyrd
A side-by-side look at the MCP Filesystem and Wyrd MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose MCP Filesystem for file systems work as a local process; choose Wyrd 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 MCP Filesystem when
- You need dedicated capabilities in the File Systems domain.
- You prefer a local stdio subprocess transport.
Choose Wyrd when
- You need dedicated capabilities in the File Systems domain.
- You prefer a local stdio subprocess transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | File Systems | File Systems |
| Quality signal | 39/100 · Fair | 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 | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 3 | 0 |
| Directory activity | 2 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View MCP Filesystem | View Wyrd |
Tools & capabilities
MCP Filesystem tools
No tool names declared yet. Check the project README from the listing page.
Wyrd 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.
MCP Filesystem
{
"mcpServers": {
"mcp-filesystem": {
"command": "npx",
"args": [
"-y",
"@ai-capabilities-suite/mcp-screenshot"
]
}
}
}
Wyrd
{
"mcpServers": {
"wyrd": {
"command": "npx",
"args": [
"-y",
"wyrd-mcp"
]
}
}
}
Frequently asked questions
MCP Filesystem is categorized under File Systems and uses a local stdio subprocess. Wyrd belongs to File Systems and uses a local stdio subprocess. Pick MCP Filesystem for file systems work and Wyrd 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 has no declared pricing — check the project's own site. Wyrd 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 mcp-filesystem and wyrd as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, MCP Filesystem has a quality signal of 39/100 (Fair) with 2 views, 0 installs and 3 GitHub stars. Wyrd has 44/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.