Render MCP

The Render MCP server lets an AI client operate a Render workspace through structured tools rather than dashboard clicks. Tools are grouped by resource. Workspace tools list the workspaces an account can reach and set the active one. Service tools create web services, static sites, cron jobs, Postgres instances and key value stores, fetch service details, and update environment variables. Deploy tools trigger a new deploy, list deploy history and return details for a single deploy. Log tools query logs with filters and list the available log label values. Metric tools return CPU, memory, instance counts, connection counts, response counts, response times and bandwidth usage. Database tools create Postgres and key value instances and run read only SQL against them. The recommended path is the hosted remote server, where a browser OAuth flow authorizes the client; an API key created in the Render dashboard also works, and the server can be run locally as a container or executable instead. The tool surface deliberately stops short of destructive and advanced operations: it does not delete resources, and it does not cover image backed services or IP allowlists, so an agent cannot quietly tear down infrastructure. It is built for solo developers and small teams already shipping on Render who want an assistant that can deploy a branch, tail the logs of a failing service, check memory pressure and run a diagnostic query in one session.