workspace-mcp
Related Servers
Alternatives to workspace-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenancePersistent project memory + architectural decisions + pre-execution safety hooks for Claude Code. Local-only storage, multi-repo workspace, automatic knowledge extraction via background auditor.28 npm14MIT
- AlicenseAqualityDmaintenanceProvides Claude Desktop with direct access to your local file system for development tasks, enabling file operations (read, write, edit), directory browsing, command execution, and codebase search within a configured projects directory.6MIT
- AlicenseNot gradedqualityCmaintenanceBridges Claude Code terminal sessions with Claude Chat by exposing session logs as tools, enabling seamless context transfer and two-way communication via a cooperative inbox and optional Google Drive sync.27 npm1MIT
- FlicenseNot gradedqualityDmaintenanceProvides filesystem access to Claude via the MCP protocol, enabling local file operations through natural language.-
- AlicenseAqualityAmaintenanceEnables Claude Code to read, create, update, and delete Claude Cowork/claude.ai projects and their knowledge documents, including syncing local folders to projects, with safety features like backups and overwrite protection.17MIT
- AlicenseNot gradedqualityCmaintenanceProvides comprehensive file system operations including reading, writing, searching, patching, code analysis, SSH transfers, and git operations, while aiming to reduce token usage in Claude Desktop.18MIT
TDQS
Scored across 22 tools
Multiple file-mutation tools overlap significantly: create_file, write_file, and update_file can all write full file content, and move_file supersedes rename_file. delete_project is essentially a specific case of delete_directory with recursive. Though descriptions are detailed, the boundaries are blurry and agents could easily select the wrong tool.
Most tool names follow a consistent verb_noun snake_case pattern (create_file, delete_directory, generate_readme, validate_workspace). The outlier is project_tree, which is a noun phrase, and it conflicts with the similarly named generate_project_tree, creating a minor inconsistency.
With 22 tools, the set feels heavy, and several tools are near-duplicates (rename_file vs move_file, write_file vs update_file), making it padded. A streamlined set of 15-18 tools could cover the same functionality without redundancy.
File CRUD, search, and project management are well covered, but there is no copy operation for files or directories, and no general rename/move for directories other than top-level projects via rename_project. These are notable gaps for a workspace management tool.