Node Dev MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GITHUB_TOKEN | Yes | The GitHub token used for authentication when setting the remote URL and pushing changes. | |
| PROJECT_REPO | Yes | The remote repository URL to be set for the git workspace. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_contentC | Search file contents in the workspace using ripgrep (rg) |
| apply_patchC | Apply a unified diff patch in the workspace |
| read_fileC | Read the content of a file in the workspace folder |
| write_fileC | Write content to a file in the workspace folder |
| delete_fileC | Delete a file from the workspace folder |
| create_folderC | Create a folder in the workspace folder |
| delete_folderC | Delete a folder from the workspace folder |
| copy_folderC | Copy a folder in the workspace folder |
| search_entriesC | Search for files and folders in the workspace using a regular expression |
| list_dirB | List files and folders in the workspace folder or a subfolder |
| vcs_statusB | Get the status of the repository |
| vcs_diffC | Get repository diff |
| vcs_logC | Show commit log |
| install_dependenciesC | Install all dependencies in the workspace |
| install_packageC | Install a single package in the workspace |
| run_buildC | Run the build script in the workspace |
| run_scriptC | Run a script in the workspace |
| start_workC | Set remote URL from env, pull latest changes, create and push a branch, and install dependencies |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.