Node Dev MCP Server
# Node Dev MCP Server
Lightweight MCP server for local workspace file operations and git commands.
## Tools
| Tool | Description | Input (JSON) |
| --- | --- | --- |
| start_work | Set remote URL from env, pull latest changes, create and push a branch, and install dependencies | `{ "branch": "feature-branch", "currentWorkingDirectory": ".", "installWithLegacyPeerDependencies": false, "startPoint": "main", "commitMessage": "Bootstrap workspace" }` |
| read_file | Read the content of a file in the workspace folder | `{ "name": "path/to/file.txt" }` |
| write_file | Write content to a file in the workspace folder | `{ "name": "path/to/file.txt", "content": "...", "commitMessage": "Update notes" }` |
| delete_file | Delete a file from the workspace folder | `{ "name": "path/to/file.txt", "commitMessage": "Remove obsolete file" }` |
| create_folder | Create a folder in the workspace folder | `{ "name": "path/to/folder", "commitMessage": "Add new folder" }` |
| delete_folder | Delete a folder from the workspace folder | `{ "name": "path/to/folder", "commitMessage": "Remove deprecated folder" }` |
| copy_folder | Copy a folder in the workspace folder | `{ "name": "path/to/folder", "newName": "path/to/new-folder", "commitMessage": "Copy folder" }` |
| search_content | Search file contents in the workspace using ripgrep (rg) | `{ "pattern": "TODO", "flags": "i", "path": "src" }` |
| apply_patch | Apply a unified diff patch in the workspace | `{ "patch": "diff --git a/foo.txt b/foo.txt\n...", "dryRun": false, "commitMessage": "Apply patch" }` |
| search_entries | Search for files and folders in the workspace using a regular expression | `{ "pattern": "src/.*\\.ts$", "flags": "i" }` |
| list_dir | List files and folders in the workspace folder or a subfolder | `{ "name": "path/to/folder" }` or `{}` |
| vcs_status | Get the status of the repository | `{}` |
| vcs_diff | Get repository diff | `{ "staged": false, "file": "path/to/file.txt" }` or `{ "base": "main", "head": "HEAD" }` |
| vcs_log | Show commit log | `{ "limit": 10 }` |
| install_dependencies | Install all dependencies in the workspace | `{ "currentWorkingDirectory": ".", "commitMessage": "Update dependencies" }` |
| install_package | Install a single package in the workspace | `{ "currentWorkingDirectory": ".", "name": "lodash@4.17.21", "commitMessage": "Add lodash" }` |
| run_build | Run the build script in the workspace | `{ "currentWorkingDirectory": ".", "commitMessage": "Build artifacts" }` |
| run_script | Run a script in the workspace | `{ "currentWorkingDirectory": ".", "script": "test", "commitMessage": "Run tests" }` |
Notes:
- `PROJECT_REPO` and `GITHUB_TOKEN` must be set so git remote/push operations can authenticate.
- `currentWorkingDirectory` must resolve to a directory inside the workspace root. Use `.` for the workspace root.
- Command tools include stdout/stderr in responses and trim long output to the last 300 lines.
TDQS
Scored across 18 tools
Most tools have distinct purposes, but there is some overlap between search_content and search_entries, which both search the workspace but differ in method (content vs. file/folder names). Additionally, run_build and run_script could be confused if build is a script, but their descriptions clarify them as separate actions. Overall, the tools are well-differentiated with only minor ambiguities.
Tool names follow a highly consistent verb_noun pattern throughout, such as apply_patch, copy_folder, and read_file. The three VCS tools (vcs_diff, vcs_log, vcs_status) use a consistent prefix, and all names are in snake_case with clear, descriptive verbs, making them predictable and easy to understand.
With 18 tools, the count is slightly high but reasonable for a Node development server covering file operations, dependency management, script execution, search, and version control. It feels comprehensive without being overly bloated, though it borders on the upper limit of typical scoping.
The toolset provides complete coverage for Node development workflows, including file CRUD (create, read, write, delete), folder management, dependency installation, build and script execution, content and file search, and version control operations (diff, log, status, branch management via start_work). There are no obvious gaps, and agents can handle end-to-end development tasks effectively.