Render MCP server for Claude, Codex and Cursor

What your AI apps can do with Render

Create and inspect services
Query logs, metrics and Postgres

Render MCP tools

26 tools, taken from the publisher's documentation on 29 October 2026. The server decides what it offers and can add or rename tools at any time; after you connect, Toolstile shows the current list.

Tool	What it does
`list_workspaces`	Lists the workspaces you can access
`select_workspace`	Sets the active workspace (deprecated; pass workspaceId per call instead)
`get_selected_workspace`	Returns the currently selected workspace
`list_services`	Lists services, optionally including previews
`get_service`	Gets details for a single service
`create_web_service`	Creates a web service from a repository or Dockerfile
`create_static_site`	Creates a static site
`create_cron_job`	Creates a cron job using a 5-field cron schedule
`update_environment_variables`	Replaces the full set of environment variables for a service
`update_web_service`	Returns a Dashboard settings link; does not modify the service
`update_static_site`	Returns a Dashboard settings link; does not modify the site
`update_cron_job`	Returns a Dashboard settings link; does not modify the cron job
`list_deploys`	Lists the deploy history for a service
`get_deploy`	Gets details for a single deploy
`trigger_deploy`	Triggers a deploy, optionally clearing the build cache
`list_events`	Lists service events such as builds, restarts and failures
`list_logs`	Lists logs matching the given filters
`list_log_label_values`	Lists the values of a log label among matching logs
`get_metrics`	Gets CPU, memory, instance, HTTP, bandwidth or connection metrics
`query_render_postgres`	Runs a read-only SQL query against a Postgres database
`list_postgres_instances`	Lists your Postgres databases
`get_postgres`	Gets details for a single Postgres database
`create_postgres`	Creates a Postgres database with a chosen plan, region and version
`list_key_value`	Lists your Key Value instances
`get_key_value`	Gets details for a single Key Value instance
`create_key_value`	Creates a Key Value instance with eviction and persistence options

Suggested access for each AI app

The documentation this list comes from doesn't mark Render's tools as read-only or destructive. Read each tool's description and decide per app before allowing it.

Coding agent in Claude Code or Cursor. Allow the read tools so the agent can look things up without stopping, and require approval for tools that change shared data.

Chat or research app in Claude Desktop. Allow reading and searching. Allow writes only where you want the app to act for you.

Unattended agent, such as a scheduled Codex job. No one is watching the session, so keep it narrow: allow what the job needs, require approval for changes and block the rest.

Blocked tools are removed from the tool list an app sees, so it won't try them. Because rules apply per app, the same Render connection can be broad in one app and read-only in another, and the credential stays in Toolstile instead of each app's config file.

How it works with Toolstile

Connect once. Add Render to a workspace (access token). Toolstile keeps the credential, so no agent config holds it.
Choose access per app. Give Claude Code every Render tool, give Cursor only the read tools, or keep Render away from an app entirely.
Share approved accounts. Teammates use the connection without copying tokens, and you can remove access in one place.
Review activity. See which app called which tool and when, so you can tighten access with evidence.

Add the Render MCP server to an AI app

Through Toolstile, every AI app uses one gateway entry, whichever servers you connect. In Claude Code:

Shell

claude mcp add --transport http toolstile 'https://mcp.toolstile.com/mcp'

Then connect Render in your workspace and choose which of its tools that app may use. Client setup covers Codex, Cursor and Claude Desktop.

To connect directly instead, add the Render endpoint to each app separately. In Claude Code:

Shell

claude mcp add --transport http render 'https://mcp.render.com/mcp'

In Cursor's mcp.json:

JSON

{
  "mcpServers": {
    "render": {
      "url": "https://mcp.render.com/mcp"
    }
  }
}

Some servers accept only clients they have approved, or need a token header. Check the Render MCP documentation for what your client needs.

Before you connect

A Render account. Sign-in uses your Render permissions.

Create an API key in your Render account settings and use it as the access token.

Server details

Detail	Value
Publisher	Render
Endpoint	`https://mcp.render.com/mcp`
Authentication	Access token
Categories	Development
Tool list	26 tools, observed 29 October 2026 (docs)

Render MCP documentation