What it does
envdoctor compares a machine's environment with what a repository says it needs. Given a repo directory, it runs five fixed checks: whether the running Node version fits the engines.node range in package.json, whether git and npm respond, whether a lockfile is present, and whether the key names in .env match those in .env.example. Each check passes or fails and names the fix. It never runs code from the repo and never prints a secret value.
It suits a check before working in an unfamiliar repository, or when a local setup fails and the missing requirement is unclear. It can be run as a CLI, where a doctor command prints a readable report or JSON, or as an MCP server on stdio that exposes a single tool, doctor_env, returning the same JSON report to an AI client.
Running it means pointing it at a repository path. The only commands it executes are git --version and npm --version. The verdict is HEALTHY when no medium or high findings exist, and ISSUES otherwise. Exit codes are 0 for HEALTHY, 1 for ISSUES and 2 for a usage error. A missing package.json skips the Node check with an info note, and the other checks still run.
Limitations and requirements
Ports, running services, databases and network reachability are not checked. Disk space is out of scope. Only the Node range syntax listed in the documentation is supported; any other syntax yields an informational RANGE-UNSUPPORTED finding instead of a pass or fail. The env file check applies only when .env.example exists.
Safety
Our team has not reviewed this resource. Only automated rules checked it; resources with high-risk signals are not published. These are signals, not a guarantee that installing it is safe. Try it in a sandbox project first.
- Runs code or changes an assistant's behaviour
Sources
- Official MCP Registry first seen 13 Nov 2026 · last seen 13 Nov 2026 · its page on the source
io.github.CloudCorpRecords/envdoctor
Local environment doctor: runtime, tools, env files, and services, pass or fail.
v0.1.0As shown on registry.modelcontextprotocol.io when we last read it