What it does
DevDoctor is a local, read-only diagnostics server that exposes five tools over stdio: diagnose_project, check_toolchain, check_environment, check_ports and explain_finding. It accepts only existing local directories, never runs repository scripts and never changes environment state. Values from .env files and URLs are redacted, and output shows variable names and safe endpoint metadata only. It makes no cloud calls.
It suits a developer who wants an assistant in Zed to inspect a local project before troubleshooting. When a Compose project is detected and the Docker engine is reachable, it reports services that have exited or are unhealthy, and it lists an unavailable engine separately from service failures. When a configured TCP port is occupied, it may add the owning PID and process name to the finding, while full executable paths are withheld. Findings use exit codes: 0 for healthy, 1 for errors or warnings, and 2 for an invalid invocation or inspection failure.
Setup involves building the release server or downloading the Windows zip from the GitHub prerelease and verifying its SHA-256 checksum. The server is then added in Zed under Settings, AI, MCP Servers, using a local server entry; the provided template needs its command value replaced with the path to your own binary. The crate is published on crates.io and listed in the official MCP Registry. It is licensed under MIT or Apache-2.0.
Limitations and requirements
IPv6 port ownership is not implemented, so an occupied IPv6 listener may have no owner evidence. Ownership lookup is available only on Windows and Linux; on other platforms, and where permissions restrict access, the port conflict is still reported without owner details. The Zed extension source is not yet published or verified in the Zed Agent UI. Compose service checks require a reachable Docker engine. Setup requires building the server or downloading and checksum-verifying the binary, and editing the configuration path to match your machine.
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
DevDoctor
Read-only local diagnostics for Rust, Node, Docker, ports, and environment configuration.
v0.1.2As shown on registry.modelcontextprotocol.io when we last read it