MCP server · Cloud and DevOps
Render MCP server
Lets an assistant create Render services and databases, trigger deploys, read logs and metrics, and run read-only SQL on Render Postgres.
- Maintainer
- Render (official)
- Licence
- Apache-2.0
- Runs
- Remote (URL)
- Sign-in
- A token or API key
- Last activity
- 2026-10-13
Overview
What it does
The Render MCP Server is hosted by Render at mcp.render.com. Official Render plugins for Claude Code, Codex and Cursor set it up with OAuth, and Claude Desktop and Codex can also sign in through the browser. For other clients and non-interactive use you create an API key in Render’s Account Settings and send it as a Bearer token. Render strongly recommends the hosted server, but the open-source Go server can also run locally as a Docker image or executable.
After you tell the assistant which workspace to use, it can create web services, static sites, cron jobs, Render Postgres databases and Key Value instances, list and inspect services, update environment variables, trigger deploys and read deploy history. It can also filter logs, fetch CPU, memory, bandwidth and response metrics and run read-only SQL queries. Other changes and deletions still need the Render Dashboard or REST API.
Tools
What the assistant can do
- Workspaces: list, select and inspect
- Create web services, static sites and cron jobs; list and inspect services
- Update a service’s environment variables
- Trigger deploys and read deploy history
- List and filter logs; fetch service and datastore metrics
- Render Postgres: create databases and run read-only SQL queries
- Render Key Value: create, list and inspect instances
Install
Install Render MCP server in your app
You need:
- A Render account
- A Render API key, unless your client signs in with OAuth
Run in your project. --scope local keeps the servers private to you in this project; use user for every project.
claude mcp add --scope local --transport http render https://mcp.render.com/mcp --header "Authorization: Bearer ${RENDER_API_KEY}"
- Set RENDER_API_KEY first, e.g. export RENDER_API_KEY=… in your shell. The command saves the value, not the variable.
Project root. Commit it to share the servers with your team; each person sets the variables in their own shell.
{
"mcpServers": {
"render": {
"type": "http",
"url": "https://mcp.render.com/mcp",
"headers": {
"Authorization": "Bearer ${RENDER_API_KEY}"
}
}
}
}
macOS: ~/Library/Application Support/Claude/claude_desktop_config.json · Windows: %APPDATA%\Claude\claude_desktop_config.json (Settings → Developer → Edit Config). Restart Claude after saving.
{
"mcpServers": {}
}
- render is a remote server: add it as a custom connector (Customize → Connectors → + Add → Add custom connector; on Team and Enterprise plans an owner adds it under Organization settings → Connectors), with the URL https://mcp.render.com/mcp.
- render: put the key in the connector’s Request headers, never in the URL.
In your project, or ~/.cursor/mcp.json for every project.
{
"mcpServers": {
"render": {
"url": "https://mcp.render.com/mcp",
"headers": {
"Authorization": "Bearer ${env:RENDER_API_KEY}"
}
}
}
}
In your workspace. VS Code asks for each secret the first time a server starts and stores it securely.
{
"inputs": [
{
"type": "promptString",
"id": "render-api-key",
"description": "RENDER_API_KEY",
"password": true
}
],
"servers": {
"render": {
"type": "http",
"url": "https://mcp.render.com/mcp",
"headers": {
"Authorization": "Bearer ${input:render-api-key}"
}
}
}
}
macOS/Linux: ~/.config/devin/mcp_config.json · Windows: %APPDATA%\devin\mcp_config.json. Read by the default Devin Local agent and by the legacy Cascade agent.
{
"mcpServers": {
"render": {
"url": "https://mcp.render.com/mcp",
"headers": {
"Authorization": "Bearer ${env:RENDER_API_KEY}"
}
}
}
}
- Devin’s docs confirm ${env:…} references for the legacy Cascade agent; for the default Devin Local agent they only document them in OAuth settings. If a server can’t authenticate, check Devin’s MCP docs.
Want it alongside other servers? Open Render MCP Server in the MCP config generator and add the rest; it writes one file per app. The snippets follow the setup in the server’s README, checked on 2026-10-14.
Before you install
- Access covers your workspaces and services, including destructive actions such as replacing a service’s environment variables and triggering deploys.
- Render tries to keep secrets such as connection strings out of the model’s context but does not guarantee it.
- A remote server sees whatever the assistant sends it. Sign in with the narrowest access the service offers. See how to choose a safe server.
Why it’s listed
Why we list it
Render’s own hosted server, updated this week, covering service creation, deploys, logs, metrics and safe database queries.
Related
More MCP servers
- Cloudflare Documentation MCP ServerLets an assistant search the current Cloudflare developer documentation through a free hosted server that needs no sign-in.
- Vercel MCPLets an assistant search Vercel docs, manage projects and deployments, read runtime logs and query Web Analytics in your Vercel account.
- Netlify MCP ServerLets an assistant create, build, deploy and manage Netlify projects, environment variables, forms and extensions in plain language.
- Supabase MCP ServerLets an assistant manage Supabase projects: list tables, run SQL and migrations, read logs, deploy Edge Functions and search the docs.
- AWS Knowledge MCP ServerLets an assistant search and read current AWS documentation, check regional availability of services and load AWS agent skills.
- Azure MCP ServerLets an assistant work with more than 45 Azure services, from Storage and Key Vault to AKS, Cosmos DB and Monitor, using your Azure sign-in.
All MCP serversMCP config generatorGuide: MCP servers in Claude CodeGuide: what is MCP?