[jacobprall]

Fixes four open issues.

• Verify the Render MCP tools with a multi-workspace API key #53 Render MCP with a multi-workspace key. This was a live bug. With a key that reaches 7 workspaces, list_services with no workspaceId returns "no workspace selected", so the architect read nothing. The Render MCP server now takes workspaceId on every resource tool and has deprecated select_workspace.
  • The PreToolUse hook sets workspaceId to RENDER_WORKSPACE_ID on every Render tool call. It replaces any value the agent passes.
  • list_workspaces and get_selected_workspace are removed from the allowlist. Once every call names the workspace, neither tool helps the architect.
  • doctor now checks that each allowlisted tool accepts workspaceId and that the workspace can be read.
• Consistent plan IDs, Blueprint validation in CI, and leftover cleanup #59 Blueprint validation in CI. render blueprints validate needs a Render login, which a fork's PR can't have. The new blueprint job checks render.yaml against the schema published at render.com/schema/render.yaml.json using check-jsonschema. The other Consistent plan IDs, Blueprint validation in CI, and leftover cleanup #59 items were already fixed in 197d236.
• Link Render's GitHub app install page in the README #67 The README and Quickstart now link the Render GitHub app and separate it from the push credential.
• Add a favicon to the gateway UI #68 Adds public/favicon.svg, served behind the same Basic Auth as the other UI files.

Testing

• npm run check: lint, typecheck, and 108 tests pass.
• npm run doctor against a real workspace passes both new MCP checks.
• check-jsonschema passes on render.yaml and fails on a file with a bad runtime.
• Not done: a full prompt-to-app run with the multi-workspace key.

Made with Cursor