Render MCP Server

Manage your Render resources from Claude, Codex, and Cursor.

Render's Model Context Protocol (MCP) server enables you to manage your Render infrastructure directly from compatible AI apps, such as Claude Code, Claude Desktop, Codex Desktop, Codex CLI, and Cursor:

Using natural language prompts, you (and your agents) can:

Create new services and redeploy existing ones
Query your databases
Analyze metrics and logs

...and more! For inspiration, see some example prompts.

What is MCP?

Model Context Protocol (MCP) is an open standard for connecting AI apps and agents to external tools and data. An MCP server exposes a set of actions that AI apps can invoke to help fulfill relevant user prompts (e.g., "Find all the documents I edited yesterday").

To perform an action, an MCP server often calls an external API, then packages the result into a standardized format for the calling application.

How it works

The Render MCP server is hosted at the following URL:

You can configure compatible AI apps (such as Claude Code, Codex, and Cursor) to communicate with this server. When you provide a relevant prompt, your tool intelligently calls the MCP server to execute supported platform actions:

Diagram of using the hosted Render MCP server with Cursor

In the example diagram above:

A user prompts Cursor to "List my Render services".
Cursor intelligently detects that the Render MCP server supports actions relevant to the prompt.
Cursor directs the MCP server to execute the list_services "tool", which calls the Render API to fetch the corresponding data.

To explore the implementation of the MCP server itself, see the open-source project:

View source on GitHub

Setup

1. Connect to the MCP server

Authenticating the MCP server grants access to your workspaces and services.

Before proceeding, make sure you're comfortable granting your AI tool access to your Render account. The MCP server supports potentially destructive operations, including modifying a service's environment variables and triggering deploys.

Official Render plugins for Claude Code, Codex, and Cursor configure this server with OAuth automatically. Select your tool below for manual setup or API-key instructions.

Claude Code setup

Select Render plugin to add the MCP server and Render's skills. For non-interactive environments, select API key instead:

In Claude Code, run the following command:
Select a scope of access for the plugin.
Run /reload-plugins.
The first time Claude uses the MCP server, it opens an authorization flow in your browser to connect your Render account.

For more details, see the Claude Code plugin documentation.

Create an API key from your Account Settings page:
Run the following command, substituting your API key where indicated:

You can include the --scope flag to specify where this MCP configuration is stored. For more details, see the Claude Code MCP documentation.

Claude Desktop setup

Select OAuth to sign in through your browser, or API key to authenticate in non-interactive environments:

In Claude Desktop, navigate to Customize > Connectors.
Search for the Render connector, then click Connect.
Complete the authorization flow in your browser.

For more details, see the Claude Desktop connector documentation.

Create an API key from your Account Settings page:
Add the configuration below to your Claude Desktop MCP settings. By default, this file is located at the following paths based on your operating system:
- macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
- Windows: %APPDATA%\Claude\claude_desktop_config.json
Replace <YOUR_API_KEY> with your API key.

For more details, see the Claude Desktop MCP documentation.

Codex Desktop and CLI setup

Select OAuth to sign in through your browser, or API key to authenticate in non-interactive environments:

Run the following command:
Complete the authorization flow in your browser to connect your Render account.

For more details, see the Codex MCP documentation.

Create an API key from your Account Settings page:
Add the following configuration to Codex's config file, ~/.codex/config.toml:

Replace <YOUR_API_KEY> with your API key.

For more details, see the Codex MCP documentation.

Cursor setup

Select Render plugin to add the MCP server and Render's skills. For non-interactive environments, select API key instead:

In a Cursor agent window, run:
Select the scope of access for the plugin, then click Add plugin.
Cursor prompts you to click Authenticate to finish the authorization flow in your browser.
- If Cursor doesn't prompt you, navigate to your MCP server settings, find the Render plugin, and click Authenticate.

For more details, see the Cursor MCP documentation.

Create an API key from your Account Settings page:
Add the following configuration to ~/.cursor/mcp.json:

Replace <YOUR_API_KEY> with your API key.

For more details, see the Cursor MCP documentation.

2. Set your workspace

To start using the Render MCP server, you first tell your AI app which Render workspace to operate in. Each MCP server action is scoped to the selected workspace.

You can set your workspace with a prompt like:

Set my Render workspace to [WORKSPACE_NAME]

Selecting an active Render workspace in Cursor

If you don't set your workspace, your app usually directs you to specify one if you submit a prompt that uses the MCP server (such as List my Render services):

Selecting an active Render workspace in Cursor

With your workspace set, you're ready to start prompting! Get started with some example prompts.

Example prompts

Your AI app can use the Render MCP server to perform a wide variety of platform actions. Here are some basic example prompts to get you started:

Service creation

Create a new database named user-db with 5 GB storage

Deploy an example Flask web service on Render using https://github.com/render-examples/flask-hello-world

Deploys

Redeploy the API service and clear the build cache

Data analysis

Using my Render database, tell me which items were the most frequently bought together

Query my read replica for daily signup counts for the last 30 days

Service metrics

What was the busiest traffic day for my service this month?

What did my service's autoscaling behavior look like yesterday?

Troubleshooting

Pull the most recent error-level logs for my API service

Why isn't my site at example.onrender.com working?

Supported actions

The Render MCP server provides a "tool" for each platform action listed below (organized by resource type). Your AI app (the "MCP host") can combine these tools however it needs to perform the tasks you describe.

For more details on all available tools, see the project README.

Resource Type	Supported Actions
Workspaces	List all workspaces you have access to Set the current workspace Fetch details of the currently selected workspace
Services	Create the following service types: Web services Static sites Cron jobs Render Postgres Render Key Value Other service types are not yet supported. List all services in the current workspace Retrieve details about a specific service Update all environment variables for a service
Deploys	Trigger a new deploy for a service List the deploy history for a service Get details about a specific deploy
Logs	List logs matching provided filters List all values for a given log label
Metrics	Fetch performance metrics for services and datastores, including: CPU / memory usage Instance count Datastore connection counts Web service response counts, segmentable by status code Web service response times (requires a Pro workspace or higher) Outbound bandwidth usage
Render Postgres	Create a new database List all databases in the current workspace Get details about a specific database Run a read-only SQL query against a specific database
Render Key Value	Create a new Key Value instance List all Key Value instances in your Render account Get details about a specific Key Value instance

Running locally

We strongly recommend using Render's hosted MCP server instead of running it locally.

The hosted MCP server automatically updates with new capabilities as they're added. Run locally only if required for your use case.

You can install and run the Render MCP server on your local machine as a Docker container, or by running the executable directly:

Docker setup

This method requires docker.

With this configuration, your AI app pulls and runs the Render MCP server as a Docker container.

Add JSON with the format below to your tool's MCP configuration (substitute <YOUR_API_KEY> with your API key):

The mcpServers key above might differ for specific tools. For example, Zed uses context_servers and GitHub Copilot uses servers. Consult your tool's documentation for details.

Local executable setup

With this configuration, your AI app runs the Render MCP server executable directly.

Install the MCP server executable using one of the methods described in Local installation, then return here.
Add JSON with the format below to your tool's MCP configuration (substitute your API key and the path to your MCP server executable):

The mcpServers key above might differ for specific tools. For example, Zed uses context_servers and GitHub Copilot uses servers. Consult your tool's documentation for details.

Local installation

Follow these instructions only if you're running the MCP server locally and without Docker.

We strongly recommend instead using Render's hosted MCP server, because it automatically updates as new capabilities are added.

View installation methods

This method requires macOS or Linux.

Run the following curl command:
Note the full path where the install script saved the downloaded executable. The output includes a message like the following:

We recommend building from source only in the following cases:

No other installation method works for your system.
You're making custom changes to the MCP server.

Install the Go programming language if you haven't already.
Clone the MCP server repository and build the executable:

This creates a render-mcp-server executable in the repo's root directory.
Note the full path to the newly built executable.

Limitations

The Render MCP server attempts to minimize exposing sensitive information (like connection strings) to your AI app's context. However, Render does not guarantee that sensitive information will not be exposed. Exercise caution when interacting with secrets in your AI app.

Note the following additional limitations:

The MCP server supports creation of the following resources:
- Web services
- Static sites
- Cron jobs
- Render Postgres databases
- Render Key Value instances
Other service types are not yet supported.
The MCP server does not support all configuration options when creating services.
- For example, you cannot create image-backed services or set up IP allowlists. If there are options you'd like to see supported, please submit an issue on the MCP server's GitHub repository.
The MCP server supports limited changes to existing Render resources:
- You can trigger a new deploy for a service, optionally clearing the build cache.
- You can modify an existing service's environment variables.
- To perform other modifications or deletions, use the Render Dashboard or REST API.
The MCP server does not support modifying scaling settings or other operational service controls.