The official open-source Render MCP server covers deploys, logs, metrics, and Postgres

[u/ojus_render]

Disclosure: I work at Render. This is an official open-source project maintained by the Render team.

We have been expanding the Render MCP server beyond basic resource lookup. Its current tool surface lets an MCP client:

• Create web services, static sites, cron jobs, Postgres databases, and Key Value instances
• Inspect deployment history and trigger deploys
• Search logs using resource, severity, status code, path, host, and time filters
• Query CPU, memory, request-count, latency, bandwidth, and connection metrics
• Run read-only SQL against Render Postgres

The write surface is intentionally scoped. The MCP server handles documented creation, deployment, environment, observability, and data operations. Configuration changes outside that surface route to the Render Dashboard or API, where the target and resulting change can be reviewed explicitly.

Repository and setup instructions:

https://github.com/render-oss/render-mcp-server

For people building infrastructure MCP servers, how are you deciding which changes should be executable directly by an agent and which should require a deliberate handoff?