env_validate — env blueprint validator MCP Tool
env_validate
(env validate) is one of 3 tools on the
env blueprint validator
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call env_validate from your client
- Claude Code env blueprint validator env_validate run in your project directory
- Claude Desktop env blueprint validator env_validate ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor env blueprint validator env_validate ~/.cursor/mcp.json
- VS Code env blueprint validator env_validate .vscode/mcp.json
- Zed env blueprint validator env_validate ~/.config/zed/settings.json
- Windsurf env blueprint validator env_validate ~/.codeium/windsurf/mcp_config.json
- Cline env blueprint validator env_validate ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI env blueprint validator env_validate ~/.gemini/settings.json
- Grok env blueprint validator env_validate .mcp.json (in your project root)
- ChatGPT env blueprint validator env_validate Settings → Connectors → Advanced → Developer mode
- Claude.ai env blueprint validator env_validate Settings → Connectors → Add custom connector
- LangChain env blueprint validator env_validate pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http env-blueprint-validator https://api.lazy-mac.com/env-blueprint-validator/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.