Env Validator

What is Env Validator?

Env Validator is an 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, such as Claude Desktop, Cursor, or Gemini CLI.

How to use Env Validator?

Clone the repository, run make build to compile the binary, then configure your MCP client (e.g., Claude Desktop) using a JSON config that points the command field to the binary path. After restarting the client, you can ask natural‑language questions like "Check if Go, Docker and Node are installed" or "Run a full environment validation."

Key features of Env Validator

• Five MCP tools: check_tool_version, check_env_vars, check_config_files, validate_environment, list_checks
• Supports 15 CLI tools: go, node, npm, docker, git, python3, etc.
• Validates semver constraints (e.g., >=1.21.0) for tool versions
• Verifies environment variables are set, non‑empty, or match a regex
• Inspects config file existence and required JSON keys
• Returns structured JSON reports with summary of OK/issue counts

Use cases of Env Validator

• Check if required developer tools are installed and meet minimum version requirements
• Verify that critical environment variables (e.g., DATABASE_URL) are defined and correctly formatted
• Validate that configuration files exist and contain expected keys before running a project
• Run a full environment sweep to get a complete health report for onboarding new machines

FAQ from Env Validator

Which AI assistants does Env Validator work with?

It works with Claude Desktop, Cursor, Gemini CLI, and any other MCP client that supports stdio‑transport MCP servers.

What CLI tools can it check?

go, node, npm, docker, git, python3, pip3, make, curl, jq, kubectl, terraform, helm, rustc, and java.

How do I specify a version constraint?

Use semver operators: >=1.21.0, >1.20.0, <=3.0.0, <3.0.0, =1.24.2, or leave empty to just check if a tool is installed.

Where does the tool run and what does it inspect?

It runs locally on your machine and inspects tools in your $PATH, environment variables from os.LookupEnv, and files/directories on the filesystem. No remote connections are made.

Is authentication or special setup required?

No authentication is needed. The server uses stdio transport with the MCP client; you only need to build the binary and add it to the client’s MCP server configuration.