# Render MCP Server (slim)

> Render's official MCP server lets an agent create services and data stores on the Render cloud platform, trigger deploys, read logs and metrics, and run read-only SQL on Render Postgres. It is hosted at mcp.render.com.

- Full: https://www.anchorterminal.com/tools/render-mcp-server.md (~7,400 tokens) · this version ~1,880 tokens · JSON https://www.anchorterminal.com/tools/render-mcp-server.json · canonical https://www.anchorterminal.com/tools/render-mcp-server
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · Updated: 2026-10-09

**B · 63.6/100 · rank #352 of 842 · #4 in Cloud & infrastructure · not agent-ready · confidence medium**


Assessment: A hosted server with 26 typed and annotated tools, OAuth or API key access and Apache-2.0 source. It cannot delete resources and wraps SQL in a read-only transaction. There are no scopes and no read-only mode, a key reaches every workspace its owner belongs to, and Render's status page recorded several major incidents in 90 days.

## Facts

- Kind: MCP server · vendor: Render Services, Inc. · category: Cloud & infrastructure · legal entity: Render Services, Inc. · provenance 97/100
- Endpoint: `https://mcp.render.com/mcp` (Streamable HTTP, stdio)
- Auth: OAuth or key · pricing: Your plan · x402: no · licence: Apache-2.0 for the server. The Render platform it acts on is a proprietary service under Render's Terms of Service
- Probe metrics: not measured yet (probes haven't run)
- Surface graded: The hosted MCP server at https://mcp.render.com/mcp. The same Go server runs locally over stdio from a binary or the image `ghcr.io/render-oss/render-mcp-server`. Render also has a REST API at https://api.render.com/v1 and a CLI, which the server does not replace
- Tools: 26. Workspaces (list, select, get selected), services (list, get, create and update for web services, static sites and cron jobs, update environment variables), deploys (list, get, trigger), `list_events`, `list_logs`, `list_log_label_values`, `get_metrics`, Postgres (list, get, create, `query_render_postgres`), Key Value (list, get, create)
- Not supported: Deleting anything, changing scaling, image-backed services, IP allowlists, private services and background workers. The docs send those to the dashboard or the REST API
- Protocol: Streamable HTTP and stdio, MCP versions 2025-11-25, 2025-06-18, 2025-03-26 and 2024-11-05 per the README
- Credentials: OAuth authorisation code with PKCE, refresh, revocation and introspection at api.render.com, no scopes in the metadata. Or a dashboard API key that does not expire and reaches every workspace of its owner
- Rate limits: Those of the REST API. 400 GET a minute, 30 a minute for other writes and for logs, 20 service creations an hour, 10 deploys a minute per service. `Ratelimit-Limit`, `Ratelimit-Remaining` and `Ratelimit-Reset` headers, with backoff and jitter advised on 429
- Audit: Workspace audit logs on the Pro plan and above, kept at least 90 days, exportable through the API. Whether MCP tool calls are marked as such was not found
- Releases: Eight tags from v0.0.1 (19 May 2025) to v0.3.0 (14 January 2026). The main branch had commits to 8 October 2026, with `list_events` added on 24 September. The hosted server shows no version
- Certifications: SOC 2 Type 2 and ISO 27001 per render.com/security, with HIPAA workspaces on the Scale plan. Reports sit behind the dashboard, and the SOC 2 report needs a Pro plan and an NDA
- Status: status.render.com on Statuspage, with components by region for web services, builds and deploys, Postgres, Key Value, the dashboard and the REST API. No component for the MCP server
- Sub-processors: Amazon Web Services, Google Cloud Platform, Cloudflare and ClickHouse Inc., all listed as United States, on render.com/security. The DPA promises ten days' notice of a new one
- Prices: Hobby workspace free per month (plan); Pro workspace $25 per month (plan); Scale workspace $499 per month (plan); Web service, 0.5 CPU and 512 MB $7 per month (plan); Web service, 1 CPU and 2 GB $25 per month (plan); Postgres, 0.1 CPU and 256 MB $6 per month (plan); Key Value, 256 MB $10 per month (plan)

- Scores: Reliability 63, Performance pending, Schema & documentation 76, Agent ergonomics 69, Security & auth 58, Payments & pricing 40, Task success pending, Maintenance & community 56, Transparency & trust 84 · total over the 7 assessed categories
- Why: Reliability, Scored as a hosted server. · Schema & documentation, Every tool declares typed inputs through mcp-go, though two open issues from 22 September 2026 report `list_logs` and `create_cron_job` acce… · Agent ergonomics, 26 tools with no toolsets or read-only subset, which an issue has requested since 8 October 2025 (15 of 25). · Security & auth, OAuth with PKCE, refresh and revocation, or a revocable API key. · Payments & pricing, No x402 or other machine payment (0). · Maintenance & community, The main branch had feature commits on 24 and 25 September 2026 and dependency commits to 8 October, and Render says the hosted server updat… · Transparency & trust, The server is Apache-2.0 and the platform is closed with clear terms (28 of 30).
- Sources: 23, open questions: 8, both in the full twin
- Capabilities: infra.cloud, code.deploy, observability.logs, observability.metrics, db.sql
- JSON: https://www.anchorterminal.com/api/v1/tools/render-mcp-server.json
- Verify (for the vendor): the badge `https://www.anchorterminal.com/badges/render-mcp-server.svg` or a link to https://www.anchorterminal.com/tools/render-mcp-server from a page on render.com or one of its subdomains, or the README of github.com/render-oss/render-mcp-server, then `POST https://www.anchorterminal.com/api/v1/verify` `{"slug", "url"}` or `verify_listing` at /mcp; re-checked weekly, no effect on the grade. Snippets in the full twin.

## Before you call it

1. Pass `workspaceId` on every resource tool call. Session-based workspace selection through `select_workspace` is deprecated and scheduled for removal.
2. Do not call `trigger_deploy` after pushing to a service with autoDeploy on. The push already starts a deploy.
3. Use an API key in the `Authorization` header for CI. OAuth grants expire and need a person to approve the browser flow again.
4. `update_environment_variables` merges by default. Set `replace` to true only to overwrite the whole set.
5. Expect 429 from the Render API at 20 service creations an hour and 10 deploys a minute per service. Back off with jitter.

## Connect

```bash
claude mcp add --transport http render https://mcp.render.com/mcp --header "Authorization: Bearer <YOUR_API_KEY>"
```
Full config and headless snippets are in the full page. Through letme (picks today, calling later): https://letme.dev/render-mcp-server

## Similar tools

| Tool | Grade | Score | Shared capabilities | Slim |
| --- | --- | --- | --- | --- |
| Grafana MCP Server | BB | 74.5 | observability.metrics, observability.logs | https://www.anchorterminal.com/tools/grafana-mcp-server.min.md |
| Honeycomb MCP | C | 58.3 | observability.metrics, observability.logs | https://www.anchorterminal.com/tools/honeycomb-mcp.min.md |
| Railway MCP Server | C | 56.7 | infra.cloud, code.deploy | https://www.anchorterminal.com/tools/railway-mcp-server.min.md |
| Datadog MCP Server | C | 56.6 | observability.metrics, observability.logs | https://www.anchorterminal.com/tools/datadog-mcp.min.md |
| Google Cloud Secret Manager | BB | 76.5 | infra.cloud | https://www.anchorterminal.com/tools/google-secret-manager.min.md |


## Panel reviews (0, desk reviews from public material, no calls made)