MCP server config linter and doctor
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., "@MCP server config linter and doctorlint my claude_desktop_config.json and diagnose failing MCP servers"
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.
MCP server config linter and doctor
Checks .mcp.json and claude_desktop_config files for missing binaries, bad env vars, duplicate server names and unreachable endpoints, then shows how to fix each one. For anyone whose MCP servers silently fail to load.
Validation Rules
This tool performs four validation checks on your MCP server configuration:
Duplicate server detection: Ensures that each server has a unique name in the configuration.
Binary existence: Checks that the binary specified for each server exists in the system PATH or is an absolute path.
Env var validation: Validates that environment variables are defined and have appropriate values (if required).
Endpoint reachability: For servers that specify an endpoint (e.g., HTTP), checks that the endpoint is reachable.
Related MCP server: MCP Observatory
Installation
pip install -e ".[dev]"Requires Python >=3.11
Usage
TODO: fill in as the build loop lands the core feature.
Example
TODO.
FAQ
What if a binary is optional?
If a binary is optional, you can mark it as such in the configuration by setting "optional": true for that server. The linter will skip the binary existence check for optional servers.
How to ignore a server?
To ignore a server during validation, add "ignore": true to the server's configuration. The linter will skip all checks for that server.
License
MIT -- see LICENSE.
This server cannot be deployed
Maintenance
Related MCP Connectors
MCP Spec Compliance MCP — audits any MCP server.json against the official Model Context Protocol
Check if your MCP server is ready to publish on the MCP Registry, Smithery, or npm.
Statically audits MCP tool surfaces for token cost, schema quality, and design issues.
Validate oh-my-posh configurations and segment snippets against the official schema.
Related MCP Servers
- AlicenseAqualityDmaintenanceEnables safe management of MCP server configuration files for AWS Q Developer and Claude Desktop, including adding, updating, removing servers, automatic backups, and validation.7MIT
- AlicenseBqualityAmaintenanceFinds problems in your MCP servers before your users do. Scans your Claude config, checks every server's capabilities, actually calls tools to make sure they work, and catches breaking changes between versions.13540 npm140MIT
- AlicenseNot gradedqualityCmaintenanceDiagnose MCP servers — health checks, tool testing, token cost audits, conflict detection, and security scanning with 50+ prompt injection patterns. Works as CLI or MCP server inside Claude Desktop.1MIT
- FlicenseNot gradedqualityCmaintenanceAn MCP (Model Context Protocol) server that inspects your local development environment and reports missing dependencies, version mismatches, and misconfigured environment variables to any MCP-compatible AI assistant. Works with Claude Desktop, Cursor, Gemini CLI, and any other client that supports stdio-transport MCP servers.-