Node Dev MCP Server
The Node Dev MCP Server is a lightweight server for local workspace file operations, git version control, and Node.js project management.
File Operations: Read, write, and delete files within the workspace
Folder Management: Create, delete, copy, and list directories
Search Functionality: Search file contents using ripgrep and find files/folders using regular expressions
Version Control: Check repository status, view diffs, show commit logs, apply unified diff patches, and track changes
Dependency Management: Install all project dependencies or individual packages
Script Execution: Run build scripts and custom npm scripts (e.g., test, lint)
Workflow Initialization: Bootstrap new feature branches with start_work (sets remote URL, pulls changes, creates/pushes branches, and installs dependencies)
Git Integration: All file/folder operations can include automatic git commits with custom messages
Environment Requirements: Requires PROJECT_REPO and GITHUB_TOKEN environment variables for git authentication. All operations are scoped to the workspace folder for security, and command outputs are trimmed to the last 300 lines for long results.
Provides tools for managing local repositories, including checking status, viewing diffs, and accessing commit logs.
Supports remote repository operations such as setting remote URLs and pushing changes using GitHub tokens.
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., "@Node Dev MCP Server start a new branch called 'feature-login' and install dependencies"
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.
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 |
|
read_file | Read the content of a file in the workspace folder |
|
write_file | Write content to a file in the workspace folder |
|
delete_file | Delete a file from the workspace folder |
|
create_folder | Create a folder in the workspace folder |
|
delete_folder | Delete a folder from the workspace folder |
|
copy_folder | Copy a folder in the workspace folder |
|
search_content | Search file contents in the workspace using ripgrep (rg) |
|
apply_patch | Apply a unified diff patch in the workspace |
|
search_entries | Search for files and folders in the workspace using a regular expression |
|
list_dir | List files and folders in the workspace folder or a subfolder |
|
vcs_status | Get the status of the repository |
|
vcs_diff | Get repository diff |
|
vcs_log | Show commit log |
|
install_dependencies | Install all dependencies in the workspace |
|
install_package | Install a single package in the workspace |
|
run_build | Run the build script in the workspace |
|
run_script | Run a script in the workspace |
|
Notes:
PROJECT_REPOandGITHUB_TOKENmust be set so git remote/push operations can authenticate.currentWorkingDirectorymust 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.
Available Tools
18 toolsapply_patchC
Apply a unified diff patch in the workspace
Inputs: patch (required), commitMessage (required), dryRun, reverse, +1 more.
copy_folderC
Copy a folder in the workspace folder
Inputs: name (required), newName (required), commitMessage (required).
create_folderC
Create a folder in the workspace folder
Inputs: name (required), commitMessage (required).
delete_fileC
Delete a file from the workspace folder
Inputs: name (required), commitMessage (required).
delete_folderC
Delete a folder from the workspace folder
Inputs: name (required), commitMessage (required).
install_dependenciesC
Install all dependencies in the workspace
Inputs: currentWorkingDirectory (required), commitMessage (required), legacyPeerDeps.
install_packageC
Install a single package in the workspace
Inputs: currentWorkingDirectory (required), name (required), commitMessage (required).
list_dirB
List files and folders in the workspace folder or a subfolder
Inputs: name.
read_fileC
Read the content of a file in the workspace folder
Inputs: name (required).
run_buildC
Run the build script in the workspace
Inputs: currentWorkingDirectory (required), commitMessage (required).
run_scriptC
Run a script in the workspace
Inputs: currentWorkingDirectory (required), script (required), commitMessage (required).
search_contentC
Search file contents in the workspace using ripgrep (rg)
Inputs: pattern (required), flags, path.
search_entriesC
Search for files and folders in the workspace using a regular expression
Inputs: pattern (required), flags.
start_workC
Set remote URL from env, pull latest changes, create and push a branch, and install dependencies
Inputs: branch (required), currentWorkingDirectory (required), commitMessage (required), installWithLegacyPeerDependencies, +1 more.
vcs_diffC
Get repository diff
Inputs: staged, file, base, head.
vcs_logC
Show commit log
Inputs: limit.
vcs_statusB
Get the status of the repository
Inputs: no named parameters.
write_fileC
Write content to a file in the workspace folder
Inputs: name (required), content (required), commitMessage (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
Maintenance
Related MCP Connectors
Manage files and folders directly from your workspace. Read and write files, list directories, cre…
Remote MCP server exposing your Node Command fleet (files, shell, processes, browser) to AI hosts.
A MCP server built for developers enabling Git based project management with project and personal…
Persistent cloud workspaces for AI agents: run commands, edit files, use git and a browser.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceThis server provides an interface for performing basic file system operations such as navigation, reading, writing, and file analysis, allowing users to manage directories and files efficiently.4-
- FlicenseNot gradedqualityDmaintenanceA FastAPI-based server that provides tools for local file management and Databricks operations, enabling users to create/edit files locally and interact with Databricks clusters, jobs, and DLT pipelines.-
- AlicenseCqualityDmaintenanceAn experimental MCP server that enables AI assistants to interact with VS Code workspaces through file operations, code execution, and Git management. It also provides tools for Docker integration, project scaffolding, and secure command execution using project-specific configurations.7622 npm3MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI clients to safely read, search, understand, and edit local project code and files, with Git inspection, code indexing, and controlled command execution within permissioned workspaces.4 npm6MIT