# Render MCP Server [Official] [Health: Active]

**Category:** ☁️ Cloud Platforms  
**Repository:** https://github.com/render-oss/render-mcp-server  
**GitHub Stars:** 200  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/render-mcp-server

## Description
Render's official MCP server. Lets AI agents create and manage Render services, databases, key-value stores, environment variables and Blueprints, and read logs, metrics and deploy history. Hosted at mcp.render.com with OAuth or an API key.

## Tools
Capabilities this server exposes over MCP:

- **list_workspaces** — List the workspaces that you have access to
- **select_workspace** — Select a workspace to use
- **ownerID** — The ID of the workspace to select (string, required). Kept as `ownerID` so
- **get_selected_workspace** — Get the currently selected workspace
- **list_services** — List all services in your Render account
- **includePreviews** — Whether to include preview services, defaults to false (boolean, optional)
- **get_service** — Get details about a specific service
- **serviceId** — The ID of the service to retrieve (string, required)
- **create_web_service** — Create a new web service in your Render account
- **name** — A unique name for your service (string, required)
- **runtime** — Runtime environment for your service (string, required). Accepted values:
- **buildCommand** — Command used to build your service (string, required unless runtime is `docker`)
- **startCommand** — Command used to start your service (string, required unless runtime is `docker`)
- **dockerfilePath** — Path to the Dockerfile relative to the repository root (string, optional). Defaults to `./Dockerfile`. Applies when runtime is `docker`.
- **dockerContext** — Build context directory relative to the repository root (string, optional). Defaults to `.`. Applies when runtime is `docker`.
- **dockerCommand** — Override for the image's startup command (string, optional). When omitted, uses the Dockerfile's `ENTRYPOINT` and `CMD`. An empty string also uses that default. Applies when runtime is `docker`.
- **repo** — Repository containing source code (string, optional)
- **branch** — Repository branch to deploy (string, optional)
- **plan** — Plan for your service (string, optional). Accepted values:
- **autoDeploy** — Whether to automatically deploy the service (string, optional). Defaults to `yes`. Accepted values:
- **yes** — Enable automatic deployments
- **no** — Disable automatic deployments
- **region** — Geographic region for deployment (string, optional). Defaults to `oregon`. Accepted values:
- **envVars** — Environment variables array (array, optional)
- **create_static_site** — Create a new static site in your Render account
- **publishPath** — Directory containing built assets (string, optional)
- **create_cron_job** — Create a new cron job in your Render account
- **schedule** — Cron schedule expression (string, required). Uses standard cron syntax with 5 fields: minute (0-59), hour (0-23), day of month (1-31), month (1-12), day of week (0-6, Sunday=0). Examples:
- **update_environment_variables** — Update all environment variables for a service
- **update_web_service** — Direct updates to a web service are not supported through the MCP server. This tool returns a link to the service's settings in the Render Dashboard, where changes can be made (or via the [Render API](https://render.com/docs/api-reference)).
- **update_static_site** — Direct updates to a static site are not supported through the MCP server. This tool returns a link to the site's settings in the Render Dashboard, where changes can be made (or via the [Render API](https://render.com/docs/api-reference)).
- **update_cron_job** — Direct updates to a cron job are not supported through the MCP server. This tool returns a link to the cron job's settings in the Render Dashboard, where changes can be made (or via the [Render API](https://render.com/docs/api-reference)).
- **list_deploys** — List deployment history for a service
- **get_deploy** — Get details about a specific deployment
- **deployId** — The ID of the deployment (string, required)
- **trigger_deploy** — Trigger a new deploy for a service. Services with autoDeploy enabled deploy automatically on push; use this for deploys that won't happen automatically.
- **clearCache** — Whether to clear the build cache before deploying (boolean, optional). Defaults to `false`.
- **list_events** — List a service's event history: deploys, builds, restarts, failures, scaling, suspensions, and disk changes. Failure events carry the reason a service went down (out-of-memory kills, non-zero exits, failed health checks, evictions), which does not appear in logs.
- **eventTypes** — Filter to specific event types (array of strings, optional). Returns all types when omitted. Accepted values:
- **startTime** — Start of the time range (RFC3339 format) (string, optional). Defaults to 7 days ago on the first page. Set it to reach events older than that.
- **endTime** — End of the time range (RFC3339 format) (string, optional). Defaults to the current time.
- **limit** — Maximum number of events to return, newest first (number, optional, min 1, max 100). Defaults to `20`.
- **cursor** — A unique string that corresponds to a position in the result list. If provided, the endpoint returns results that appear after the corresponding position. To fetch the first page of results, set to the empty string (string, optional).
- **list_logs** — List logs matching the provided filters
- **resource** — Filter logs by their resource (array of strings, required)
- **level** — Filter logs by their severity level (array of strings, optional)
- **type** — Filter logs by their type (array of strings, optional)
- **instance** — Filter logs by the instance they were emitted from (array of strings, optional)
- **host** — Filter request logs by their host (array of strings, optional)
- **statusCode** — Filter request logs by their status code (array of strings, optional)
- **method** — Filter request logs by their requests method (array of strings, optional)
- **path** — Filter request logs by their path (array of strings, optional)
- **text** — Filter by the text of the logs (array of strings, optional)
- **direction** — The direction to query logs for (string, optional)
- **list_log_label_values** — List all values for a given log label in the logs matching the provided filters
- **label** — The label to list values for (string, required)
- **get_metrics** — Get performance metrics for any Render resource (services, Postgres databases, key-value stores). Metrics may be empty if the metric is not valid for the given resource
- **resourceId** — The ID of the resource to get metrics for (service ID, Postgres ID, or key-value store ID) (string, required)
- **metricTypes** — Which metrics to fetch (array of strings, required). Accepted values:
- **cpu_usage** — CPU usage metrics (available for all resources)
- **cpu_limit** — CPU resource constraints (available for all resources)
- **cpu_target** — CPU autoscaling thresholds (available for all resources)
- **memory_usage** — Memory usage metrics (available for all resources)
- **memory_limit** — Memory resource constraints (available for all resources)
- **memory_target** — Memory autoscaling thresholds (available for all resources)
- **instance_count** — Instance count metrics (available for all resources)
- **http_request_count** — HTTP request count metrics (services only)
- **http_latency** — HTTP response time metrics (services only)
- **bandwidth_usage** — Bandwidth usage metrics (services only)
- **active_connections** — Active connection metrics (databases and key-value stores only)
- **resolution** — Time resolution for data points in seconds. Lower values provide more granular data. Higher values provide more aggregated data points. API defaults to 60 seconds if not provided, minimum 30 seconds (number, optional)
- **cpuUsageAggregationMethod** — Method for aggregating CPU usage metric values over time intervals (string, optional). Defaults to `AVG`. Accepted values:
- **AVG** — Average CPU usage over time intervals
- **MAX** — Maximum CPU usage over time intervals
- **MIN** — Minimum CPU usage over time intervals
- **aggregateHttpRequestCountsBy** — Field to aggregate HTTP request count metrics by (string, optional). When not specified, returns total request counts. Accepted values:
- **httpLatencyQuantile** — The quantile/percentile of HTTP latency to fetch. Only supported for http_latency metric. Common values: 0.5 (median), 0.95 (95th percentile), 0.99 (99th percentile). Defaults to 0.95 if not specified (number, optional, min: 0.0, max: 1.0)
- **httpHost** — Filter HTTP metrics to specific request hosts. Supported for http_request_count and http_latency metrics. Example: 'api.example.com' or 'myapp.render.com'. When not specified, includes all hosts (string, optional)
- **httpPath** — Filter HTTP metrics to specific request paths. Supported for http_request_count and http_latency metrics. Example: '/api/users' or '/health'. When not specified, includes all paths (string, optional)
- **query_render_postgres** — Run a read-only SQL query against a Render-hosted Postgres database

## Claude Desktop Quick Installation
No confirmed install details yet, so no config is published. Follow the setup steps in the repository above.

## Documentation

## What Render MCP Server does

Render MCP Server gives MCP-compatible AI clients access to Render workspaces and resources. It is intended for infrastructure and application operations such as creating services, reviewing deployment activity, inspecting logs and performance metrics, and working with databases and key-value stores.

The server can create web services, static sites, and cron jobs. It also supports listing and inspecting services, updating a service’s complete environment-variable set, and working with deployment history. Render Blueprints are included among the supported resource areas.

## How it works

Workspace access is explicit. Agents can list available workspaces, select one, and retrieve the selected workspace. Resource calls can also receive a workspace identifier directly, which keeps the target workspace clear across MCP reconnects and transport-session changes. Omitting that identifier temporarily falls back to the workspace selected in the active session.

The hosted endpoint is `mcp.render.com`. Authentication can use OAuth or an API key. The server supports both Streamable HTTP and stdio transports, with MCP protocol versions `2025-11-25`, `2025-06-18`, `2025-03-26`, and `2024-11-05`; stdio also supports the sessionless `2026-07-28` protocol. Streamable HTTP clients must perform the MCP initialization handshake.

## Setup and configuration

Connect an MCP client to the hosted Render endpoint using the authentication method supported by the client, or configure the server through stdio. Render’s MCP server documentation provides the official connection instructions at `https://render.com/docs/mcp-server`.

When creating a web service or cron job, provide the runtime and build and start commands unless using Docker. Supported runtimes include Node, Python, Go, Rust, Ruby, Elixir, and Docker. Repository, branch, plan, region, automatic-deployment behavior, and environment variables can be supplied where applicable.

## Tools and capabilities

- List, select, and inspect Render workspaces.
- List services, optionally including preview services, and retrieve service details.
- Create web services, static sites, and scheduled cron jobs.
- Configure supported runtimes, repositories, branches, regions, plans, commands, and environment variables during creation.
- Replace a service’s complete environment-variable list.
- List deployment history, inspect individual deployments, and trigger deployments.
- Read application logs, service metrics, deployment status, databases, key-value stores, and Blueprints.

Cron schedules use standard five-field cron syntax. Docker-based services and cron jobs can specify a Dockerfile path, build context, and startup command. Deploying a prebuilt image from a container registry is not supported.

## Limitations and notes

The web-service, static-site, and cron-job update tools do not apply changes directly. They return a link to the relevant Render Dashboard settings page, where changes can be made manually or through the Render API.

Workspace selection through the deprecated `ownerID` parameter remains available for compatibility, but new resource calls should pass `workspaceId` directly. Automatic deployments default to enabled when creating supported services unless disabled. Web services and cron jobs default to the Oregon region when no region is supplied.

_Full upstream README: https://allmcps.com/mcp/render-mcp-server/readme_