convez.ai
MCP ServerDevOps & InfraestruturaAvançado
watilde

Node Core MCP

watilde/node-core-mcp

Acesso direto ao Node.js core para build, test e code review via IA

Ver no GitHub
BomPluginScore · de 0 a 100

Servidor MCP que oferece acesso direto a um repositório local do Node.js, permitindo compilar, testar, buscar código e revisar mudanças via assistentes de IA. Integra-se com Claude, Cursor e VS Code para fluxo de trabalho colaborativo em contribuições ao Node.js.

Instalação

$npx convez-ai watilde/node-core-mcp

1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.

Métricas

Estrelas
1
Forks
0
Acompanhando
0
Saúde
71%
Último commit
há 5 meses
Versão
—
Issues abertas
0
Contribuidores
1

Casos de uso

  • Contribuições ao Node.js com assistência de IA
  • Debugging e análise de falhas de teste
  • Busca e navegação de código na base do Node.js
  • Automação de build, lint e testes durante desenvolvimento

Veredito

Ferramente altamente especializada para contribuidores do Node.js que necessitam integração profunda com CI/build. Bem estruturada com suporte multi-cliente (Claude, Cursor, VS Code), mas requer setup manual e dependências externas (gh CLI, node-core-utils).

README

A tradução para o português deste README ainda está na fila.

node-core-mcp

An MCP server that gives AI assistants hands-on access to a local nodejs/node checkout — build, test, search, and review, all from the conversation.

Requirements

  • Node.js ≥ 18
  • A local clone of nodejs/node
  • gh CLI (only for get_pr_metadata)

Installation

npm install -g node-core-mcp

Or use directly with npx:

npx node-core-mcp --repo /path/to/node

MCP configuration

By default (no --repo flag), the server resolves the repo root as three directories above the bin/ folder — which works when the package lives inside the repo at tools/node-core-mcp/.

Claude Code

~/.claude/settings.json (global) or .claude/settings.json (project):

{
  "mcpServers": {
    "node-core": {
      "command": "node-core-mcp",
      "args": ["--repo", "/absolute/path/to/nodejs/node"]
    }
  }
}

Cursor

~/.cursor/mcp.json (global) or .cursor/mcp.json (project):

{
  "mcpServers": {
    "node-core": {
      "command": "node-core-mcp",
      "args": ["--repo", "/absolute/path/to/nodejs/node"]
    }
  }
}

VS Code

Requires VS Code 1.99+ with the GitHub Copilot extension. .vscode/mcp.json:

{
  "servers": {
    "node-core": {
      "type": "stdio",
      "command": "node-core-mcp",
      "args": ["--repo", "${workspaceFolder}/../node"]
    }
  }
}

Codex CLI

~/.codex/config.toml:

[mcp_servers.node-core]
command = "node-core-mcp"
args = ["--repo", "/absolute/path/to/nodejs/node"]

Tools

Build

ToolDescription
configureRun ./configure (accepts debug, extra_flags)
buildRun make (accepts target, jobs)
run_lintRun make lint-js, make lint-cpp, or make lint
get_node_versionGet the version of the local dev build (falls back to system Node.js)

Test

ToolDescription
run_testRun a single test file with the dev binary
run_testsRun tests matching a pattern via tools/test.py
run_benchmarkRun a benchmark file with the dev binary
explain_test_failureParse TAP / tools/test.py output and return failures + re-run commands
verify_changeDetect changed files via git, rebuild only when required, run the relevant tests, and return parsed results. Skips the rebuild entirely for JS-only changes when the binary was configured with --node-builtin-modules-path

Code search

ToolDescription
search_codegrep -rn across lib/, src/, test/ (or a custom dir)
read_fileRead a source file (supports offset and limit for large files)
git_logShow recent commit history, optionally filtered by path

Documentation

ToolDescription
list_docsList Markdown files in doc/api/
read_docRead a single API doc (e.g. stream.md)
search_docsSearch doc/api/, doc/contributing/, and test/README.md

Jenkins CI

Requires node-core-utils (ncu-ci) configured with a Jenkins API token, and an authenticated gh CLI.

ToolDescription
start_ciStart a node-test-pull-request Jenkins run for a PR via ncu-ci run
get_ci_statusFetch parsed Jenkins results for a PR or job URL via ncu-ci url --json
classify_failureAnswer "known flake or real regression?" by cross-referencing nodejs/node flaky-test issues and recent nodejs/reliability reports

PR & subsystem

ToolDescription
find_subsystemGiven changed files, identify the primary subsystem, likely reviewers, and PR labels
list_relevant_testsGiven changed files, suggest tests via the lib/ require graph and a test-name index (not just path heuristics)
get_pr_metadataFetch labels, CI status, reviews, and commits for a nodejs/node PR via gh

Development

# Run the test suite (submodule required)
git submodule update --init
npm test

Tests that require a dev binary (get_node_version, run_test) are automatically skipped unless the binary has been built. To build it:

npm run setup  # git submodule update --init + configure + make

CI runs the test suite on Node.js 18, 20, and 22 for every push to main and every pull request. A full build with npm run setup runs weekly (Sundays) to verify the dev-binary-dependent tests.

License

MIT

Ver o original no GitHub

Bom para

Relacionados