Render Mcp

by render-osse8f889396634MIT1 starsListed Oct 8, 2026Updated Oct 8, 2026Repository updated today

Connects and configures the Render MCP server for AI coding tools—setup per tool (Cursor, Claude Code, Codex), authentication, workspace selection, tool catalog, and troubleshooting. Use when MCP is not configured, list_services() fails, the user asks about Render MCP setup, or an action skill needs MCP but it's not connected yet. Trigger terms: MCP, Render MCP, list_services, MCP setup, MCP server, OAuth, API key, Bearer token, mcp.render.com, workspace selection.

Instructions only

Render MCP Server

The Render MCP server lets AI coding tools manage Render services, databases, deploys, logs, and metrics directly. This skill covers setup, authentication, workspace selection, the tool catalog, and troubleshooting.

Action skills (render-deploy, render-debug, render-monitor) use MCP tools for their workflows. If MCP is not connected, set it up using this skill first.

When to Use

  • list_services() fails or MCP tools are unavailable
  • First-time Render MCP setup for any AI tool
  • User asks how to connect their AI tool to Render
  • Switching workspaces or troubleshooting auth errors
  • Discovering which MCP tools exist and what they do

Connection Details

PropertyValue
URLhttps://mcp.render.com/mcp
TransportHTTP (streamable)
AuthOAuth when installed via the Render plugin (pre-registered client id); bearer token (API key) for manual setup
API key pagehttps://dashboard.render.com/u/*/settings#api-keys (manual setup)
Docshttps://render.com/docs/mcp-server

Setup by Tool

Render plugin (recommended)

The Render plugin for Cursor, Codex, and Claude Code bundles this MCP server with a pre-registered OAuth client id, so no API key is needed. After installing or updating the plugin, reload the tool (restart Cursor or Claude Code, or start a new Codex thread) so it loads the plugin-provided MCP server, then complete the Render OAuth prompt the first time MCP tools are used. Verify with list_services().

The manual, API-key setups below are for tools without the plugin or for custom MCP configurations.

Cursor

  1. Get an API key from the Render Dashboard

  2. Add to ~/.cursor/mcp.json:

json
{  "mcpServers": {    "render": {      "url": "https://mcp.render.com/mcp",      "headers": {        "Authorization": "Bearer <YOUR_API_KEY>"      }    }  }}
  1. Restart Cursor, then verify with list_services()

Claude Code

  1. Get an API key from the Render Dashboard

  2. Add the MCP server:

bash
claude mcp add --transport http render https://mcp.render.com/mcp --header "Authorization: Bearer <YOUR_API_KEY>"
  1. Restart Claude Code, then verify with list_services()

Codex

  1. Get an API key from the Render Dashboard

  2. Set the key in your shell:

bash
export RENDER_API_KEY="<YOUR_API_KEY>"
  1. Add the MCP server:
bash
codex mcp add render --url https://mcp.render.com/mcp --bearer-token-env-var RENDER_API_KEY
  1. Restart Codex, then verify with list_services()

Other Tools

For tools not listed above, use the generic HTTP MCP configuration:

  • URL: https://mcp.render.com/mcp
  • Auth header: Authorization: Bearer <YOUR_API_KEY>
  • Transport: HTTP (streamable HTTP, not SSE)

See Render MCP docs for tool-specific instructions.

Workspace Selection

After MCP is connected, set the active workspace:

Set my Render workspace to [WORKSPACE_NAME]

Or programmatically:

get_selected_workspace()   # Check currentlist_workspaces()          # List available

All MCP operations run against the active workspace.

Tool Catalog

Service management

ToolPurpose
list_services()List all services and datastores
get_service(serviceId)Get service details
create_web_service(...)Create a web service from Git repo
create_static_site(...)Create a static site from Git repo
update_service(serviceId, ...)Update service configuration
restart_service(serviceId)Restart a service

Deploys

ToolPurpose
list_deploys(serviceId, limit)List deploys for a service
trigger_deploy(serviceId)Trigger a new deploy

Logs

ToolPurpose
list_logs(resource, level, type, text, statusCode, limit)Query logs with filters

Key filters: level (error, warn, info), type (build, deploy), text (search string), statusCode (HTTP codes).

Metrics

ToolPurpose
get_metrics(resourceId, metricTypes, ...)Get service or database metrics

Metric types: cpu_usage, memory_usage, cpu_limit, memory_limit, http_latency, http_request_count, active_connections.

Optional: httpLatencyQuantile (0.5, 0.95, 0.99), httpPath (filter by endpoint).

Databases

ToolPurpose
list_postgres_instances()List Postgres databases
get_postgres(postgresId)Get database details
query_render_postgres(postgresId, sql)Run SQL query

Key Value

ToolPurpose
list_key_value()List Key Value instances
get_key_value(keyValueId)Get Key Value details

Environment Variables

ToolPurpose
update_environment_variables(serviceId, envVars)Set env vars on a service

Workspace

ToolPurpose
list_workspaces()List available workspaces
get_selected_workspace()Get the active workspace

Common Mistakes

MistakeFix
Wrong URL (using SSE endpoint)Use https://mcp.render.com/mcp (not /sse)
Plugin installed but MCP tools unavailableReload the tool (restart, or start a new thread) so it loads the plugin's MCP server
OAuth prompt does not appearReinstall or update the Render plugin, then reload the tool
Expired or invalid API keyGenerate a new key from Dashboard > Account Settings > API Keys
Wrong workspace selectedRun list_workspaces() and switch to the correct one
Using MCP to create image-backed servicesNot supported — use Dashboard or API for prebuilt Docker images
Missing Bearer prefix in auth headerHeader must be Authorization: Bearer <key>

Troubleshooting

See references/troubleshooting.md for connection errors, auth failures, timeout issues, and tool-specific quirks.

References

DocumentContents
references/troubleshooting.mdConnection errors, auth failures, tool-specific issues, timeout handling

Related Skills

  • render-deploy — Deploy flows using MCP tools
  • render-debug — Debug failures using MCP logs and metrics
  • render-monitor — Monitor health using MCP metrics
  • render-cli — CLI alternative when MCP is unavailable

Source and attribution

Source:render-oss/render-plugin-claude-codeinskills/render-mcpat commite8f8893

License: MIT

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal

More from render-oss/render-plugin-claude-code

Render Static Sites

render-oss

Guides deploying and configuring static sites and SPAs on Render's CDN, covering builds, routing, headers and PR previews.

DevOps & Cloud1updated today

Render Scaling

render-oss

Guides scaling of Render web services, private services and background workers, covering instance counts, autoscaling and cost.

DevOps & Cloud1updated today

Render Networking

render-oss

Explains Render private networking: internal DNS, service discovery, ports, and cross-service connectivity.

DevOps & Cloud1updated today

Render Postgres

render-oss

Guides setup, connection, storage, HA, replicas and backups for Render Managed PostgreSQL databases.

DevOps & Cloud1updated today

Render Monitor

render-oss

Monitors Render cloud services in real time: health checks, performance metrics, logs, and database status.

DevOps & Cloud1updated today

Render Domains

render-oss

Configures custom domains and TLS certificates on Render—DNS setup, CNAME records, apex domains, wildcard domains, and certificate troubleshooting. Use when the user needs to add a custom domain, configure DNS, set up HTTPS/TLS, troubleshoot certificate issuance, disable the onrender.com subdomain, or add a wildcard domain. Trigger terms: custom domain, DNS, CNAME, TLS, SSL, HTTPS, certificate, apex domain, wildcard domain, onrender.com, domain verification.

Awaiting classification1updated today
Render Mcp Agent Skill | SourceWeft