onboard-mcp
Checks if Docker is installed and the daemon is running.
Compares keys in .env files against .env.example to ensure required environment variables are present.
Checks if Git is installed and user.name/user.email are configured.
Checks if the current Node.js version matches the project requirements from .nvmrc or package.json engines.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@onboard-mcp run the doctor on my project, it needs ports 3000 and 5432"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
onboard-mcp
Your dev environment, fixed by asking your AI assistant.
An MCP (Model Context Protocol) server that checks the things that silently break local development: wrong Node version, Docker not running, missing git config, missing .env keys, busy ports. Ask your AI assistant "is my environment ready?" and get a pass/fail report with the exact fix for everything that's broken.
Why
Every developer has lost an afternoon to "it works on my machine": the app fails because Node is one major version off, or the port is taken by a zombie process, or .env.local is missing a key that was added last sprint. On my team, environment setup issues cost every new developer days.
This server turns that debugging into one question in your AI chat:
You: run the doctor on my project, it needs ports 3000 and 5432
Assistant:
[PASS] node-version: Node v20.11.0 satisfies the project requirement (20). [FAIL] docker: Docker is installed but the daemon is not running. Fix: Start Docker Desktop, or on Linux run "sudo systemctl start docker". [PASS] git-config: Git is installed and user.name / user.email are configured. [FAIL] env-files: .env.local is missing 1 key(s) from .env.example: REDIS_URL. Fix: Add the missing keys to .env.local. Ask a teammate or your secrets manager for the values. [PASS] ports: All required ports are free: 3000, 5432. 2 failing, 0 warning(s). Fixes listed above.
Related MCP server: DevEnv Doctor MCP
Tools
Tool | What it checks |
| Runs everything below and returns one report |
| Current Node vs |
| Docker CLI installed and daemon running |
| git installed, |
|
|
| Whether the TCP ports your project needs are free |
Requirements
Node.js 18 or newer — required for every client, since the server runs via
npx onboard-mcp. Check withnode --version; install from nodejs.org if needed.
That's the only universal dependency. npx fetches the published package automatically — no clone or build required. The Claude Code steps below additionally need the claude CLI (npm install -g @anthropic-ai/claude-code); other clients do not.
Quick start
Claude Code
Requires the Claude Code CLI. Install it first if you don't have it:
npm install -g @anthropic-ai/claude-codeThen register the server:
claude mcp add --scope user onboard -- npx -y onboard-mcp(--scope user makes it available in every project; omit it to register for the current project only.) Verify with claude mcp get onboard.
Or clone and build locally:
git clone https://github.com/developerpankajdixit/onboard-mcp.git
cd onboard-mcp && npm install && npm run build
claude mcp add onboard -- node /absolute/path/to/onboard-mcp/dist/index.jsVS Code (GitHub Copilot agent mode)
Add to .vscode/mcp.json in your project:
{
"servers": {
"onboard": {
"command": "npx",
"args": ["-y", "onboard-mcp"]
}
}
}Cursor
Settings → MCP → Add new global MCP server, or add to .cursor/mcp.json:
{
"mcpServers": {
"onboard": {
"command": "npx",
"args": ["-y", "onboard-mcp"]
}
}
}Claude Desktop
Add to claude_desktop_config.json:
{
"mcpServers": {
"onboard": {
"command": "npx",
"args": ["-y", "onboard-mcp"]
}
}
}Then ask: "Run the doctor on /path/to/my/project, it needs ports 3000 and 5432."
Any other MCP-compatible client works the same way: point it at npx -y onboard-mcp over stdio.
Design notes
Fixes, not just failures. Every failing check returns the exact command to fix it, so the assistant can offer to run it.
Secrets never leave your machine. The env check compares key names only. Values are never included in any tool response.
Pure check functions. Every check is a plain async function with injectable dependencies, tested without mocking the MCP layer (23 unit tests, CI on Linux and macOS across Node 18/20/22).
Development
npm install
npm test # vitest
npm run build # tsc
npm run dev # run the server from sourceRoadmap
fix_*counterpart tools that apply the suggested fixes after confirmationConfigurable check list via an
onboard.config.jsonin the project rootDatabase connectivity checks (Postgres, Redis) behind a flag
License
MIT. Built by Pankaj Dixit, based on an internal MCP onboarding tool that cut new-developer setup from 2 weeks to under 30 minutes.
Available Tools
6 toolscheck_dockerA
Check whether Docker is installed and the daemon is running.
Inputs: no named parameters.
check_env_filesA
Compare .env/.env.local against .env.example and report missing keys (keys only, values are never read into the response).
Inputs: projectDir.
check_git_configA
Check whether git is installed and user.name / user.email are configured.
Inputs: no named parameters.
check_node_versionB
Check whether the current Node.js version matches the project's .nvmrc or package.json engines requirement.
Inputs: projectDir.
check_portsB
Check whether the given TCP ports are free on localhost.
Inputs: ports (required).
doctorB
Run every environment check (Node version, Docker, git config, env files, ports) and return a full report with fixes.
Inputs: ports, projectDir.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 6 tools
Each tool has a clearly distinct purpose: env file comparison, port checking, node version, Docker, git config, and a comprehensive doctor. No ambiguity between tools.
Five tools follow the 'check_' prefix pattern, but 'doctor' breaks the pattern. This is a minor inconsistency overall.
6 tools is well-scoped for an environment onboarding server, covering essential checks without being excessive or too sparse.
Covers key environment checks like Node version, Docker, git config, env files, and ports. Minor gaps like package manager or OS checks, but sufficient for basic onboarding.
Maintenance
Related MCP Connectors
Exact developer checks: email DNS, Supabase RLS, cron, JSON, contrast, time zones, npm/PyPI packages
Stop your agent before it runs rm -rf /etc or emails your .env. Deterministic preflight checks.
Checks AI-written code for leaked keys and made-up packages, on your machine. Never uploads code.
Local checks for sudo, systemd, sshd, ufw, and secret leaks before an agent applies them.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceProvides tools for local development environment management and PostgreSQL optimization, including version checking, port process termination, SQL query analysis, and index suggestions.5-
- AlicenseAqualityDmaintenanceEnables LLM clients to inspect local development environment, including Docker container health, pnpm workspace integrity, and stuck process diagnosis.4MIT
- AlicenseNot gradedqualityDmaintenanceEnables LLM clients to inspect local dev environments—Docker container health, pnpm workspace integrity, and stuck process detection—without manual terminal copy-pasting.MIT
- AlicenseAqualityDmaintenanceLocal Dev Doctor turns an unfamiliar development checkout into an evidence-backed diagnosis. It discovers how the project is meant to run, checks safe prerequisites, and executes only the exact probe that a user approves.9MIT