DevSpace File Tools
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@DevSpace File Toolscopy src/config.json to src/config.backup.json"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
DevSpace File Tools
English | 简体中文
Adds dedicated copy, move, and delete MCP tools to @waishnav/devspace.
The goal is to keep filesystem mutations structured and workspace-scoped instead of falling back to shell cp, mv, or rm commands.
What it adds
After patching, DevSpace minimal/full mode exposes:
open_workspace
read
write
edit
copy
move
delete
bashThe added tools enforce the same workspace boundary model as DevSpace:
paths must stay inside the opened workspace;
workspace root and
.gitare protected;symlinked parent directories may not escape the workspace;
copyrefuses to overwrite by default;directory copies require
recursive=true;moverefuses to overwrite by default;deleting a non-empty directory requires
recursive=true;symlinks are copied/deleted as symlinks instead of following their targets;
DevSpace instructions are updated so shell
cp,mv, andrmare not used as a bypass.
Related MCP server: ABSD DevOps MCP Server
Compatibility
Currently tested against:
DevSpace package | Status |
| ✅ Tested |
Unknown DevSpace versions are refused by default rather than being patched against unverified internal anchors.
If a future DevSpace release ships all three tools natively, the patch exits successfully without changing anything.
Install
Requirements:
Node.js supported by your DevSpace installation
an existing
@waishnav/devspaceinstallation
One-line install
Recommended:
npx --yes github:ZntxCYL/devspace-file-toolsNo npm publication is required: npx installs this package directly from the GitHub repository and runs its single CLI entry.
Alternatively, using the shell bootstrap:
curl -fsSL https://raw.githubusercontent.com/ZntxCYL/devspace-file-tools/main/install.sh | bashThe bootstrap installer downloads patch.mjs from this repository, applies it, then removes the temporary copy.
If you prefer to inspect the files first:
git clone https://github.com/ZntxCYL/devspace-file-tools.git
cd devspace-file-tools
bash install.shThe installer looks for DevSpace in these locations:
$DEVSPACE_PACKAGE_ROOTwhen explicitly set;./node_modules/@waishnav/devspace;~/.local/share/devspace-kit/node_modules/@waishnav/devspace;the global npm root.
For a custom installation with npx:
DEVSPACE_PACKAGE_ROOT=/path/to/node_modules/@waishnav/devspace \
npx --yes github:ZntxCYL/devspace-file-toolsOr with the shell bootstrap:
curl -fsSL https://raw.githubusercontent.com/ZntxCYL/devspace-file-tools/main/install.sh | \
DEVSPACE_PACKAGE_ROOT=/path/to/node_modules/@waishnav/devspace bashFrom a cloned repository:
DEVSPACE_PACKAGE_ROOT=/path/to/node_modules/@waishnav/devspace bash install.shRestart DevSpace after patching, then reconnect your MCP client so it refreshes the tool schema.
What the patch changes
The patch modifies DevSpace's generated dist/server.js and creates a timestamped backup before writing changes:
~/.devspace/patches/backups/It is idempotent: running it again on an already-patched installation is a no-op.
Because this modifies generated package output, reinstalling or upgrading @waishnav/devspace can replace the patch. Run ./install.sh again after an upgrade. If the new version is not explicitly supported, the patch will stop instead of guessing.
Updating DevSpace
A safe workflow is:
cd ~/.local/share/devspace-kit
npm install --save-exact @waishnav/devspace@latest
cd /path/to/devspace-file-tools
bash install.shIf the patch reports an unsupported DevSpace version, wait for this repository to add compatibility for that release or open an issue with the exact DevSpace version.
Uninstall
The cleanest uninstall is to reinstall the official DevSpace package at the version you want, which restores its original generated files.
For example, in a local DevSpace kit:
npm install --save-exact @waishnav/devspace@1.0.8Why not shell commands?
copy, move, and delete are model-facing mutations. Dedicated MCP tools can validate workspace boundaries and make intent explicit before touching the filesystem. Shell commands are broader and much easier to misuse accidentally.
License
MIT
This server cannot be deployed
Maintenance
Related MCP Connectors
Manage files and folders directly from your workspace. Read and write files, list directories, cre…
Securely search and manage workspace context files for AI agents and teams.
Your workspace as agent tools — docs, canvases, slides, sheets, projects, tickets, and a shell.
Develop, manage, and debug Railway projects, services, and deployments from within agents.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceProvides secure file system operations for AI assistants including directory listing, file reading/writing, deletion, searching, and copying. Features safety controls like path validation, permission checks, and file size limits.-
- AlicenseNot gradedqualityFmaintenanceEnables secure local filesystem operations and interactive terminal sessions for AI assistants. Provides 12 tools for file management, directory operations, code searching, and running interactive REPLs with security protections.11MIT
- AlicenseNot gradedqualityCmaintenanceProvides secure, sandboxed file system access for AI assistants to read, write, and manage project files with controlled command execution capabilities, all confined to a designated workspace directory.MIT
- FlicenseNot gradedqualityDmaintenanceEnables AI assistants to safely interact with the file system through a set of tools for reading, writing, deleting, copying, moving files, and managing directories.-