Render MCP Server

About

Render's official MCP server connects AI coding tools directly to your Render cloud infrastructure — create and manage web services, static sites, background workers, cron jobs, and PostgreSQL/Redis databases without leaving your editor. The primary integration path is Render's hosted server at mcp.render.com/mcp, authenticated with a scoped Render API key generated from your Account Settings page; configure it in Cursor, Codex, Claude Code (via `claude mcp add --transport http`), Claude Desktop (via the `mcp-remote` bridge), or Jules with a few lines of JSON. Render also publishes the underlying implementation as an open-source Go project (render-oss/render-mcp-server) for teams that want to inspect or self-host the tool-calling logic. Core tools span workspace selection (list_workspaces, select_workspace), service management (list_services, get_service, create_web_service, create_static_site, create_cron_job with full runtime/plan/region options), deploy triggers, log and metrics inspection for debugging failed builds, and direct Postgres database queries from inside the LLM. Render explicitly flags that the server currently supports one potentially destructive action — modifying an existing service's environment variables — so it scopes API keys broadly but keeps write operations narrow. Typical prompts include "deploy this repo as a new Node web service in Oregon" or "show me the last 100 log lines for my API service and tell me why it's crashing." Because it's a hosted remote server, there's no local runtime to keep updated, and Render ships new tools directly through mcp.render.com without requiring a client-side package upgrade.

Installation

claude mcp add --transport http render https://mcp.render.com/mcp --header "Authorization: Bearer <YOUR_API_KEY>"

Categories

Works With

Frequently Asked Questions