# Render — MCP Server

> Create services, trigger deploys, read logs and metrics, and query Postgres on Render.

**Source:** https://mcpplaygroundonline.com/mcp-servers/render  
**Transport:** http  
**Requires auth:** Yes

---

## What it does

Every action is scoped to one workspace, which you set first with a prompt such as “set my Render workspace to Acme”. From there the agent can create web services, static sites, cron jobs, Postgres databases and Key Value instances; list, read and update services; trigger deploys and read deploy history; filter logs; and read metrics such as CPU, memory, instance count, response codes and times, and bandwidth. Postgres access is read-only SQL. The limits are deliberate: the server does not delete resources, updates are limited to environment variables, and it creates only those five service types. That shape suits the questions an on-call engineer asks — why did the last deploy fail, what changed in error rate — without letting an agent tear anything down.

## Tools exposed

- workspaces — list workspaces, set the current one and read its details
- services — create web services, static sites, cron jobs, Postgres and Key Value; list, read and update
- deploys — trigger a deploy, list history and read deploy details
- logs — list logs with filters and list label values
- metrics — CPU, memory, instances, connections, response codes and times, bandwidth
- postgres — create databases, read their details and run read-only SQL

## Example queries you can run

- "Set my workspace to Acme, then tell me why the last deploy of the api service failed."
- "Show 5xx responses for the web service over the last hour and the log lines around the spike."
- "Which of my services used the most memory this week?"
- "Run a read-only query on the orders database: how many orders were created today?"

## Details

- **Recommended model:** anthropic/claude-sonnet-4.5 — Debugging a deploy means joining deploy history, logs and metrics across several calls. Sonnet 4.5 keeps that chain straight and reports what it actually found.
- **Transport:** http
- **Authentication:** Required — OAuth for interactive clients, or a Render API key as a bearer token. The server acts within the workspace you select.
- **Hosted endpoint:** https://mcp.render.com/mcp
- **Official source:** [Render MCP Server documentation](https://render.com/docs/mcp-server)

## Connecting to Render

### Client configuration

**API key**

For clients that do not support OAuth. Create the key in your Render account settings.

```
{
  "mcpServers": {
    "render": {
      "type": "http",
      "url": "https://mcp.render.com/mcp",
      "headers": {
        "Authorization": "Bearer <RENDER_API_KEY>"
      }
    }
  }
}
```

## Frequently asked questions

### Can the Render MCP server delete services?

No. Render’s server does not support deleting resources, so an agent cannot tear down a service or database through it.

### Why does it ask me to set a workspace?

Every action is scoped to one workspace. Set it first with a prompt such as “set my Render workspace to Acme”, and the agent works only inside that workspace.

### Can it change my service configuration?

Only environment variables. Other settings, such as IP allowlists, are not supported through the server.

### Can it query my database?

Yes, with read-only SQL on Render Postgres. It cannot write to the database.

### Is it safe with production?

Safer than most infrastructure servers, because there are no deletes and Postgres is read-only. It can still trigger deploys and change environment variables, and Render notes it does not guarantee sensitive values will never appear in output, so start with a staging workspace.

---

_Test this server across 40+ models on MCP Playground: https://mcpplaygroundonline.com/mcp-servers/render — free, no install._