Local Workspace MCP vs MCP File Tools
A side-by-side look at the Local Workspace MCP and MCP File Tools MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Local Workspace MCP for file systems work; choose MCP File Tools for file systems over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Local Workspace MCP when
- You need dedicated capabilities in the File Systems domain.
- Its auth model fits you: No auth required.
Choose MCP File Tools when
- You need dedicated capabilities in the File Systems domain.
- You prefer a remote HTTP/SSE transport.
- You want tools like
read_text_file, read_multiple_files, write_whole_file.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | File Systems | File Systems |
| Quality signal | 32/100 · Emerging | 52/100 · Good |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Remote HTTP/SSE |
| 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 | 0 | 1 |
| Directory activity | 0 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | Not listed | 41 |
| Full listing | View Local Workspace MCP | View MCP File Tools |
Tools & capabilities
Local Workspace MCP tools
No tool names declared yet. Check the project README from the listing page.
MCP File Tools tools 41
read_text_fileread_multiple_fileswrite_whole_fileedit_fileedit_file_applypreviewIdpatch_packagepatch_package_applylist_directorytreeget_file_infofilesystem_package- +29 more on 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.
Local Workspace MCP
No confirmed install command for Local Workspace MCP yet — follow the setup steps linked from its listing page rather than a guessed package name.
MCP File Tools
{
"mcpServers": {
"mcp-file-tools": {
"url": "http://127.0.0.1:8765/mcp"
}
}
}
Frequently asked questions
Local Workspace MCP is categorized under File Systems and uses an install path we have not confirmed yet. MCP File Tools belongs to File Systems and uses a remote HTTP/SSE transport. Pick Local Workspace MCP for file systems work and MCP File Tools 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. Local Workspace MCP has no confirmed install command yet — follow its own setup instructions.
Local Workspace MCP is listed as free. Auth: no auth required. MCP File Tools 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 local-workspace-mcp and mcp-file-tools as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Local Workspace MCP has a quality signal of 32/100 (Emerging) with 0 views, 0 installs and 0 GitHub stars. MCP File Tools has 52/100 (Good) with 1 views, 0 installs and 1 GitHub stars.