← All labs

Render

by docker ✓ verified ✓ Packaged by Docker

Interact with your Render resources via LLMs.

MCP server installable needs setup network: on runtime: sysbox

DevOps MCP Servers

Render MCP Server

Interact with your Render resources via LLMs.

What is an MCP Server?

MCP Info

Attribute	Details
Docker Image	mcp/render
Author	render-oss
Repository	https://github.com/render-oss/render-mcp-server

Image Building Info

Attribute	Details
Dockerfile	https://github.com/render-oss/render-mcp-server/blob/031b723587057ab702a73d18729f6cbbd8dd972a/Dockerfile
Commit	`031b723587057ab702a73d18729f6cbbd8dd972a`
Docker Image built by	Docker Inc.
Docker Scout Health Score	Docker Scout Health Score
Verify Signature	`COSIGN_REPOSITORY=mcp/signatures cosign verify mcp/render --key https://raw.githubusercontent.com/docker/keyring/refs/heads/main/public/mcp/latest.pub`
Licence	Apache License 2.0

Available Tools (24)

Tools provided by this Server	Short Description
`create_cron_job`	Create cron job
`create_key_value`	Create Key Value instance
`create_postgres`	Create Postgres instance
`create_static_site`	Create static site
`create_web_service`	Create web service
`get_deploy`	Get deploy details
`get_key_value`	Get Key Value instance details
`get_metrics`	Get resource metrics
`get_postgres`	Get Postgres instance details
`get_selected_workspace`	Get selected workspace
`get_service`	Get service details
`list_deploys`	List deploys
`list_key_value`	List Key Value instances
`list_log_label_values`	List log label values
`list_logs`	List logs
`list_postgres_instances`	List Postgres instances
`list_services`	List services
`list_workspaces`	List workspaces
`query_render_postgres`	Query Postgres
`select_workspace`	Select workspace
`update_cron_job`	Update cron job
`update_environment_variables`	Update environment variables
`update_static_site`	Update static site
`update_web_service`	Update web service

Tools Details

Tool: `create_cron_job`

Create a new cron job in your Render account. A cron job is a scheduled task that runs on a recurring schedule specified using cron syntax. Cron jobs are ideal for background tasks like data processing, cleanup operations, sending emails, or generating reports. By default, these services are automatically deployed when the specified branch is updated. This tool is currently limited to support only a subset of the cron job configuration parameters. It also only supports cron jobs which don't use Docker, or a container registry. To create a cron job without those limitations, please use the dashboard at: https://dashboard.render.com/create

Parameters	Type	Description
`buildCommand`	`string`	The command used to build your cron job. For example, 'npm install' for Node.js or 'pip install -r requirements.txt' for Python.
`name`	`string`	A unique name for your cron job.
`runtime`	`string`	The runtime environment for your cron job. This determines how your job is built and run.
`schedule`	`string`	The cron schedule expression that determines when the job runs. 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: '0 0 * * ' (daily at midnight), '/15 * * * ' (every 15 minutes), '0 9 * 1-5' (weekdays at 9am), '0 0 1 * *' (first day of each month at midnight). For natural language requests like 'every hour' or 'daily at 3pm', convert to cron syntax.
`startCommand`	`string`	The command that runs when your cron job executes. For example, 'node scripts/cleanup.js' for Node.js or 'python scripts/process_data.py' for Python.
`autoDeploy`	`string` optional	Whether to automatically deploy the cron job when the specified branch is updated. Defaults to 'yes'.
`branch`	`string` optional	The repository branch to deploy. This branch will be deployed when you manually trigger deploys and when auto-deploy is enabled. If left empty, this will fall back to the default branch of the repository.
`envVars`	`array` optional	Environment variables to set for your cron job. These are exposed during builds and at runtime.
`plan`	`string` optional	The pricing plan for your cron job. Different plans offer different levels of resources and features.
`region`	`string` optional	The geographic region where your cron job will be deployed. Defaults to Oregon.
`repo`	`string` optional	The repository containing the source code for your cron job. Must be a valid Git URL that Render can clone and deploy. Do not include the branch in the repo string. You can instead supply a 'branch' parameter.

This tool interacts with external entities.

Tool: `create_key_value`

Create a new Key Value instance in your Render account

Parameters	Type	Description
`name`	`string`	Name of the Key Value instance
`maxmemoryPolicy`	`string` optional	The eviction policy for the Key Value store
`plan`	`string` optional	Pricing plan for the Key Value instance
`region`	`string` optional	Region where the Key Value instance will be deployed

This tool interacts with external entities.

Tool: `create_postgres`

Create a new Postgres instance in your Render account

Parameters	Type	Description
`name`	`string`	The name of the database as it will appear in the Render Dashboard
`diskSizeGb`	`number` optional	Your database's capacity, in GB. You can increase storage at any time, but you can't decrease it. Specify 1 GB or any multiple of 5 GB.
`plan`	`string` optional	Pricing plan for the database
`region`	`string` optional	Region where the database will be deployed
`version`	`number` optional	PostgreSQL version to use (e.g., 14, 15)

This tool interacts with external entities.

Tool: `create_static_site`

Create a new static site in your Render account. Apps that consist entirely of statically served assets (commonly HTML, CSS, and JS). Static sites have a public onrender.com subdomain and are served over a global CDN. Create a static site if you're building with a framework like: Create React App, Vue.js, Gatsby, etc.This tool is currently limited to support only a subset of the static site configuration parameters.To create a static site without those limitations, please use the dashboard at: https://dashboard.render.com/static/new

Parameters	Type	Description
`buildCommand`	`string`	Render runs this command to build your app before each deploy. For example, 'yarn; yarn build' a React app.
`name`	`string`	A unique name for your service. This will be used to generate the service's URL if it is public.
`autoDeploy`	`string` optional	Whether to automatically deploy the service when the specified branch is updated. Defaults to 'yes'.
`branch`	`string` optional	The repository branch to deploy. This branch will be deployed when you manually trigger deploys and when auto-deploy is enabled. If left empty, this will fall back to the default branch of the repository.
`envVars`	`array` optional	Environment variables to set for your service. These are exposed during builds and at runtime.
`publishPath`	`string` optional	The relative path of the directory containing built assets to publish. Examples: ./, ./build, dist and frontend/build. This is the directory that will be served to the public.
`repo`	`string` optional	The repository containing the source code for your service. Must be a valid Git URL that Render can clone and deploy. Do not include the branch in the repo string. You can instead supply a 'branch' parameter.

This tool interacts with external entities.

Tool: `create_web_service`

Create a new web service in your Render account. A web service is a public-facing service that can be accessed by users on the internet. By default, these services are automatically deployed when the specified branch is updated and do not require a manual trigger of a deploy. The user should only be prompted to manually trigger a deploy if auto-deploy is disabled.This tool is currently limited to support only a subset of the web service configuration parameters.It also only supports web services which don't use Docker, or a container registry.To create a service without those limitations, please use the dashboard at: https://dashboard.render.com/web/new

Parameters	Type	Description
`buildCommand`	`string`	The command used to build your service. For example, 'npm run build' for Node.js or 'pip install -r requirements.txt' for Python.
`name`	`string`	A unique name for your service. This will be used to generate the service's URL if it is public.
`runtime`	`string`	The runtime environment for your service. This determines how your service is built and run.
`startCommand`	`string`	The command used to start your service. For example, 'npm start' for Node.js or 'gunicorn app:app' for Python.
`autoDeploy`	`string` optional	Whether to automatically deploy the service when the specified branch is updated. Defaults to 'yes'.
`branch`	`string` optional	The repository branch to deploy. This branch will be deployed when you manually trigger deploys and when auto-deploy is enabled. If left empty, this will fall back to the default branch of the repository.
`envVars`	`array` optional	Environment variables to set for your service. These are exposed during builds and at runtime.
`plan`	`string` optional	The pricing plan for your service. Different plans offer different levels of resources and features.
`region`	`string` optional	The geographic region where your service will be deployed. Defaults to Oregon. Choose the region closest to your users for best performance.
`repo`	`string` optional	The repository containing the source code for your service. Must be a valid Git URL that Render can clone and deploy. Do not include the branch in the repo string. You can instead supply a 'branch' parameter.

This tool interacts with external entities.

Tool: `get_deploy`

Retrieve the details of a particular deploy for a particular service.

Parameters	Type	Description
`deployId`	`string`	The ID of the deployment to retrieve
`serviceId`	`string`	The ID of the service to get deployments for

This tool is read-only. It does not modify its environment.

This tool interacts with external entities.

Tool: `get_key_value`

Retrieve a Key Value instance by ID

Parameters	Type	Description
`keyValueId`	`string`	The ID of the Key Value instance to retrieve

This tool is read-only. It does not modify its environment.

This tool interacts with external entities.

Tool: `get_metrics`

Get performance metrics for any Render resource (services, Postgres databases, key-value stores). Supports CPU usage/limits/targets, memory usage/limits/targets, service instance counts, HTTP request counts and response time metrics, bandwidth usage metrics, database active connection counts for debugging, capacity planning, and performance optimization. Returns time-series data with timestamps and values for the specified time range. HTTP metrics support filtering by host and path for more granular analysis. Limits and targets help understand resource constraints and autoscaling thresholds. Metrics may be empty if the metric is not valid for the given resource.

Parameters	Type	Description
`metricTypes`	`array`	Which metrics to fetch. CPU usage/limits/targets, memory usage/limits/targets, and instance count metrics are available for all resources. HTTP request counts and response time metrics, and bandwidth usage metrics are only available for services. Active connection metrics are only available for databases and key-value stores. Limits show resource constraints, targets show autoscaling thresholds.
`resourceId`	`string`	The ID of the resource to get metrics for (service ID, Postgres ID, or key-value store ID)
`aggregateHttpRequestCountsBy`	`string` optional	Field to aggregate HTTP request metrics by. Only supported for http_request_count metric. Options: host (aggregate by request host), statusCode (aggregate by HTTP status code). When not specified, returns total request counts.
`cpuUsageAggregationMethod`	`string` optional	Method for aggregating metric values over time intervals. Only supported for CPU usage metrics. Options: AVG, MAX, MIN. Defaults to AVG.
`endTime`	`string` optional	End time for metrics query in RFC3339 format (e.g., '2024-01-01T13:00:00Z'). Defaults to the current time. The end time must be within the last 30 days.
`httpHost`	`string` optional	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.
`httpLatencyQuantile`	`number` optional	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.
`httpPath`	`string` optional	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.
`resolution`	`number` optional	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. There is a limit to the number of data points that can be returned, after which the metrics endpoint will return a 500. If you are getting a 500, try reducing granularity (increasing the value of resolution).
`startTime`	`string` optional	Start time for metrics query in RFC3339 format (e.g., '2024-01-01T12:00:00Z'). Defaults to 1 hour ago. The start time must be within the last 30 days.

This tool is read-only. It does not modify its environment.

This tool interacts with external entities.

Tool: `get_postgres`

Retrieve a Postgres instance by ID

Parameters	Type	Description
`postgresId`	`string`	The ID of the Postgres instance to retrieve

This tool is read-only. It does not modify its environment.

This tool interacts with external entities.

Tool: `get_selected_workspace`

Get the currently selected workspace

Tool: `get_service`

Get details about a specific service

Parameters	Type	Description
`serviceId`	`string`	The ID of the service to retrieve

This tool is read-only. It does not modify its environment.

This tool interacts with external entities.

Tool: `list_deploys`

List deploys matching the provided filters. If no filters are provided, all deploys for the service are returned.

Parameters	Type	Description
`serviceId`	`string`	The ID of the service to get deployments for
`cursor`	`string` optional	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.
`limit`	`number` optional	The maximum number of deploys to return in a single page. To fetch additional pages of results, set the cursor to the last deploy in the previous page. It should be rare to need to set this value greater than 20.

This tool is read-only. It does not modify its environment.

This tool interacts with external entities.

Tool: `list_key_value`

List all Key Value instances in your Render account

Tool: `list_log_label_values`

List all values for a given log label in the logs matching the provided filters. This can be used to discover what values are available for filtering logs using the list_logs tool. You can query for logs across multiple resources, but all resources must be in the same region and belong to the same owner.

Parameters	Type	Description
`label`	`string`	The label to list values for.
`resource`	`array`	Filter by resource. A resource is the id of a server, cronjob, job, postgres, or redis.
`direction`	`string` optional	The direction to query logs for. Backward will return most recent logs first. Forward will start with the oldest logs in the time range.
`endTime`	`string` optional	End time for log query (RFC3339 format). Defaults to the current time. The end time must be within the last 30 days.
`host`	`array` optional	Filter request logs by their host. Wildcards and regex are supported.
`instance`	`array` optional	Filter logs by the instance they were emitted from.
`level`	`array` optional	Filter logs by their severity level. Wildcards and regex are supported.
`method`	`array` optional	Filter request logs by their requests method. Wildcards and regex are supported.
`path`	`array` optional	Filter request logs by their path. Wildcards and regex are supported.
`startTime`	`string` optional	Start time for log query (RFC3339 format). Defaults to 1 hour ago. The start time must be within the last 30 days.
`statusCode`	`array` optional	Filter request logs by their status code. Wildcards and regex are supported.
`text`	`array` optional	Filter by the text of the logs. Wildcards and regex are supported.
`type`	`array` optional	Filter logs by their type.

This tool is read-only. It does not modify its environment.

This tool interacts with external entities.

Tool: `list_logs`

List logs matching the provided filters. Logs are paginated by start and end timestamps. There are more logs to fetch if hasMore is true in the response. Provide the nextStartTime and nextEndTime timestamps as the startTime and endTime query parameters to fetch the next page of logs. You can query for logs across multiple resources, but all resources must be in the same region and belong to the same owner.

Parameters	Type	Description
`resource`	`array`	Filter logs by their resource. A resource is the id of a server, cronjob, job, postgres, or redis.
`direction`	`string` optional	The direction to query logs for. Backward will return most recent logs first. Forward will start with the oldest logs in the time range.
`endTime`	`string` optional	End time for log query (RFC3339 format). Defaults to the current time. The end time must be within the last 30 days.
`host`	`array` optional	Filter request logs by their host. Wildcards and regex are supported.
`instance`	`array` optional	Filter logs by the instance they were emitted from. An instance is the id of a specific running server.
`level`	`array` optional	Filter logs by their severity level. Wildcards and regex are supported.
`limit`	`number` optional	Maximum number of logs to return
`method`	`array` optional	Filter request logs by their requests method. Wildcards and regex are supported.
`path`	`array` optional	Filter request logs by their path. Wildcards and regex are supported.
`startTime`	`string` optional	Start time for log query (RFC3339 format). Defaults to 1 hour ago. The start time must be within the last 30 days.
`statusCode`	`array` optional	Filter request logs by their status code. Wildcards and regex are supported.
`text`	`array` optional	Filter by the text of the logs. Wildcards and regex are supported.
`type`	`array` optional	Filter logs by their type. Types include app for application logs, request for request logs, and build for build logs. You can find the full set of types available for a query by using the list_log_label_values tool.

This tool is read-only. It does not modify its environment.

This tool interacts with external entities.

Tool: `list_postgres_instances`

List all Postgres databases in your Render account

Tool: `list_services`

List all services in your Render account

Parameters	Type	Description
`includePreviews`	`boolean` optional	Whether to include preview services in the response. Defaults to false.

This tool is read-only. It does not modify its environment.

This tool interacts with external entities.

Tool: `list_workspaces`

List the workspaces that you have access to

Tool: `query_render_postgres`

Run a read-only SQL query against a Render-hosted Postgres database. This tool creates a new connection for each query and closes it after the query completes.

Parameters	Type	Description
`postgresId`	`string`	The ID of the Postgres instance to query
`sql`	`string`	The SQL query to run. Note that the query will be wrapped in a read-only transaction.

This tool is read-only. It does not modify its environment.

This tool interacts with external entities.

Tool: `select_workspace`

Select a workspace to use for all actions. This tool should only be used after explicitly asking the user to select one, it should not be invoked as part of an automated process. Having the wrong workspace selected can lead to destructive actions being performed on unintended resources.

Parameters	Type	Description
`ownerID`	`string`	The ID of the owner to select

This tool interacts with external entities.

Tool: `update_cron_job`

Update an existing cron job in your Render account.

Parameters	Type	Description
`serviceId`	`string`	The ID of the service to update

This tool is read-only. It does not modify its environment.

Tool: `update_environment_variables`

Update environment variables for a service. By default, environment variables passed in will be merged with the service's existing environment variables. This makes it safe to update environment variableswithout pulling the existing ones into the MCP host's context. To replace all existing environment variables, set the 'replace' parameter to 'true'.

Parameters	Type	Description
`envVars`	`array`	The list of environment variables to update or set for the service.
`serviceId`	`string`	The ID of the service to update
`replace`	`boolean` optional	Whether to replace all existing environment variables with the provided list, or merge with the existing ones. Defaults to false.

This tool may perform destructive updates.

This tool interacts with external entities.

Tool: `update_static_site`

Update an existing static site in your Render account.

Parameters	Type	Description
`serviceId`	`string`	The ID of the service to update

This tool is read-only. It does not modify its environment.

Tool: `update_web_service`

Update an existing web service in your Render account.

Parameters	Type	Description
`serviceId`	`string`	The ID of the service to update

This tool is read-only. It does not modify its environment.

Use this MCP Server

{
  "mcpServers": {
    "render": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "RENDER_API_KEY",
        "mcp/render"
      ],
      "env": {
        "RENDER_API_KEY": "DUMMY"
      }
    }
  }
}

Why is it safer to run MCP Servers with Docker?

Install

Open LabStore on any connected Selfmade Ninja Labs instance and press Get — or run this from the instance shell:

labsctl store-install mcp-render

About

Kind: MCP server
Publisher: docker
Version: f9f9352e6329
Updated: 13 Oct 2026
Transport: stdio
Licence: Apache License 2.0
Owner: render-oss
Packaged by: Docker

Secrets needed

RENDER_API_KEY: render.api_key

Tools (24)

create_cron_job: Create a new cron job in your Render account. A cron job is a scheduled task that runs on a recurring schedule specified using cron syntax. Cron jobs are ideal
create_key_value: Create a new Key Value instance in your Render account
create_postgres: Create a new Postgres instance in your Render account
create_static_site: Create a new static site in your Render account. Apps that consist entirely of statically served assets (commonly HTML, CSS, and JS). Static sites have a public
create_web_service: Create a new web service in your Render account. A web service is a public-facing service that can be accessed by users on the internet. By default, these servi
get_deploy: Retrieve the details of a particular deploy for a particular service.
get_key_value: Retrieve a Key Value instance by ID
get_metrics: Get performance metrics for any Render resource (services, Postgres databases, key-value stores). Supports CPU usage/limits/targets, memory usage/limits/targets
get_postgres: Retrieve a Postgres instance by ID
get_selected_workspace: Get the currently selected workspace
get_service: Get details about a specific service
list_deploys: List deploys matching the provided filters. If no filters are provided, all deploys for the service are returned.
list_key_value: List all Key Value instances in your Render account
list_log_label_values: List all values for a given log label in the logs matching the provided filters. This can be used to discover what values are available for filtering logs using
list_logs: List logs matching the provided filters. Logs are paginated by start and end timestamps. There are more logs to fetch if hasMore is true in the response. Provid
list_postgres_instances: List all Postgres databases in your Render account
list_services: List all services in your Render account
list_workspaces: List the workspaces that you have access to
query_render_postgres: Run a read-only SQL query against a Render-hosted Postgres database. This tool creates a new connection for each query and closes it after the query completes.
select_workspace: Select a workspace to use for all actions. This tool should only be used after explicitly asking the user to select one, it should not be invoked as part of an
update_cron_job: Update an existing cron job in your Render account.
update_environment_variables: Update environment variables for a service. By default, environment variables passed in will be merged with the service's existing environment variables. This m
update_static_site: Update an existing static site in your Render account.
update_web_service: Update an existing web service in your Render account.

Source

View upstream ↗

View repository ↗

image mcp/render@sha256:96ee41e6433a8da9844d6b46cc72e9ab296dffbf5a56cd70dce049c203906d7b

digest sha256:96ee41e6433a8da9844…

Every store app is stripped of privileged/host-mount settings at install and runs contained on the installing host. The rules.

Render MCP Server

MCP Info

Image Building Info

Available Tools (24)

Tools Details

Tool: create_cron_job

Tool: create_key_value

Tool: create_postgres

Tool: create_static_site

Tool: create_web_service

Tool: get_deploy

Tool: get_key_value

Tool: get_metrics

Tool: get_postgres

Tool: get_selected_workspace

Tool: get_service

Tool: list_deploys

Tool: list_key_value

Tool: list_log_label_values

Tool: list_logs

Tool: list_postgres_instances

Tool: list_services

Tool: list_workspaces

Tool: query_render_postgres

Tool: select_workspace

Tool: update_cron_job

Tool: update_environment_variables

Tool: update_static_site

Tool: update_web_service

Use this MCP Server

Tool: `create_cron_job`

Tool: `create_key_value`

Tool: `create_postgres`

Tool: `create_static_site`

Tool: `create_web_service`

Tool: `get_deploy`

Tool: `get_key_value`

Tool: `get_metrics`

Tool: `get_postgres`

Tool: `get_selected_workspace`

Tool: `get_service`

Tool: `list_deploys`

Tool: `list_key_value`

Tool: `list_log_label_values`

Tool: `list_logs`

Tool: `list_postgres_instances`

Tool: `list_services`

Tool: `list_workspaces`

Tool: `query_render_postgres`

Tool: `select_workspace`

Tool: `update_cron_job`

Tool: `update_environment_variables`

Tool: `update_static_site`

Tool: `update_web_service`