VS Code env blueprint validator env_validate
How to: VS Code env blueprint validator env_validate
Add env blueprint validator to VS Code
-
01
Open .vscode/mcp.json and merge this in. Keep any servers already there.
{
"servers": {
"env-blueprint-validator": {
"type": "http",
"url": "https://api.lazy-mac.com/env-blueprint-validator/mcp"
}
}
}-
02
Save the file and restart VS Code.
-
03
Ask for something env_validate does. VS Code lists the server's tools on connect and calls env_validate itself — you do not invoke it by name.
-
04
If nothing happens, check the server is running and that env blueprint validator's identifier in your config matches the one above exactly.
Requires agent mode. MCP: Open User Configuration puts the same block in every workspace. VS Code docs
Same tool, other clients
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.