Skip to main content
Glama
Node Dev MCP Server
by LiamCarver

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.

Available Tools

18 tools
apply_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

    B3.3/5.0

    Scored across 18 tools

    Disambiguation4/5

    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.

    Naming Consistency5/5

    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.

    Tool Count4/5

    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.

    Completeness5/5

    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

    ActivityInactive
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers

    • F
      license
      Not graded
      quality
      D
      maintenance
      This 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
      -
    • F
      license
      Not graded
      quality
      D
      maintenance
      A 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.
      -
    • A
      license
      C
      quality
      D
      maintenance
      An 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.
      76
      22 npm
      3
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables 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 npm
      6
      MIT