Render

Render

Interact with your Render resources via LLMs.

2.1K

1

22 Tools

Signed
Built by Docker
Requires Secrets
Add to Docker Desktop

Version 4.43 or later needs to be installed to add the server automatically

Use cases

About

Render MCP Server

Interact with your Render resources via LLMs.

What is an MCP Server?

Characteristics

AttributeDetails
Docker Imagemcp/render
Authorrender-oss
Repositoryhttps://github.com/render-oss/render-mcp-server
Dockerfilehttps://github.com/render-oss/render-mcp-server/blob/main/Dockerfile
Docker Image built byDocker Inc.
Docker Scout Health ScoreDocker Scout Health Score
Verify SignatureCOSIGN_REPOSITORY=mcp/signatures cosign verify mcp/render --key https://raw.githubusercontent.com/docker/keyring/refs/heads/main/public/mcp/latest.pub
LicenceApache License 2.0

Available Tools (22)

Tools provided by this ServerShort Description
create_key_valueCreate Key Value instance
create_postgresCreate Postgres instance
create_static_siteCreate static site
create_web_serviceCreate web service
get_deployGet deploy details
get_key_valueGet Key Value instance details
get_metricsGet resource metrics
get_postgresGet Postgres instance details
get_selected_workspaceGet selected workspace
get_serviceGet service details
list_deploysList deploys
list_key_valueList Key Value instances
list_log_label_valuesList log label values
list_logsList logs
list_postgres_instancesList Postgres instances
list_servicesList services
list_workspacesList workspaces
query_render_postgresQuery Postgres
select_workspaceSelect workspace
update_environment_variablesUpdate environment variables
update_static_siteUpdate static site
update_web_serviceUpdate web service

Tools Details

Tool: create_key_value

Create a new Key Value instance in your Render account

ParametersTypeDescription
namestringName of the Key Value instance
planstringPricing plan for the Key Value instance
maxmemoryPolicystringoptionalThe eviction policy for the Key Value store
regionstringoptionalRegion 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

ParametersTypeDescription
namestringThe name of the database as it will appear in the Render Dashboard
planstringPricing plan for the database
diskSizeGbnumberoptionalYour 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.
regionstringoptionalRegion where the database will be deployed
versionnumberoptionalPostgreSQL 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

ParametersTypeDescription
buildCommandstringRender runs this command to build your app before each deploy. For example, 'yarn; yarn build' a React app.
namestringA unique name for your service. This will be used to generate the service's URL if it is public.
autoDeploystringoptionalWhether to automatically deploy the service when the specified branch is updated. Defaults to 'yes'.
branchstringoptionalThe 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.
envVarsarrayoptionalEnvironment variables to set for your service. These are exposed during builds and at runtime.
publishPathstringoptionalThe 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.
repostringoptionalThe 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

ParametersTypeDescription
buildCommandstringThe command used to build your service. For example, 'npm run build' for Node.js or 'pip install -r requirements.txt' for Python.
namestringA unique name for your service. This will be used to generate the service's URL if it is public.
runtimestringThe runtime environment for your service. This determines how your service is built and run.
startCommandstringThe command used to start your service. For example, 'npm start' for Node.js or 'gunicorn app:app' for Python.
autoDeploystringoptionalWhether to automatically deploy the service when the specified branch is updated. Defaults to 'yes'.
branchstringoptionalThe 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.
envVarsarrayoptionalEnvironment variables to set for your service. These are exposed during builds and at runtime.
planstringoptionalThe pricing plan for your service. Different plans offer different levels of resources and features.
regionstringoptionalThe geographic region where your service will be deployed. Defaults to Oregon. Choose the region closest to your users for best performance.
repostringoptionalThe 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.

ParametersTypeDescription
deployIdstringThe ID of the deployment to retrieve
serviceIdstringThe 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

ParametersTypeDescription
keyValueIdstringThe 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.

ParametersTypeDescription
metricTypesarrayWhich 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.
resourceIdstringThe ID of the resource to get metrics for (service ID, Postgres ID, or key-value store ID)
aggregateHttpRequestCountsBystringoptionalField 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.
cpuUsageAggregationMethodstringoptionalMethod for aggregating metric values over time intervals. Only supported for CPU usage metrics. Options: AVG, MAX, MIN. Defaults to AVG.
endTimestringoptionalEnd 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.
httpHoststringoptionalFilter 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.
httpLatencyQuantilenumberoptionalThe 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.
httpPathstringoptionalFilter 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.
resolutionnumberoptionalTime 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).
startTimestringoptionalStart 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

ParametersTypeDescription
postgresIdstringThe 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

ParametersTypeDescription
serviceIdstringThe 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.

ParametersTypeDescription
serviceIdstringThe ID of the service to get deployments for
cursorstringoptionalA 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.
limitnumberoptionalThe 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.

ParametersTypeDescription
labelstringThe label to list values for.
resourcearrayFilter by resource. A resource is the id of a server, cronjob, job, postgres, or redis.
directionstringoptionalThe direction to query logs for. Backward will return most recent logs first. Forward will start with the oldest logs in the time range.
endTimestringoptionalEnd time for log query (RFC3339 format). Defaults to the current time. The end time must be within the last 30 days.
hostarrayoptionalFilter request logs by their host. Wildcards and regex are supported.
instancearrayoptionalFilter logs by the instance they were emitted from.
levelarrayoptionalFilter logs by their severity level. Wildcards and regex are supported.
methodarrayoptionalFilter request logs by their requests method. Wildcards and regex are supported.
patharrayoptionalFilter request logs by their path. Wildcards and regex are supported.
startTimestringoptionalStart time for log query (RFC3339 format). Defaults to 1 hour ago. The start time must be within the last 30 days.
statusCodearrayoptionalFilter request logs by their status code. Wildcards and regex are supported.
textarrayoptionalFilter by the text of the logs. Wildcards and regex are supported.
typearrayoptionalFilter 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.

ParametersTypeDescription
resourcearrayFilter logs by their resource. A resource is the id of a server, cronjob, job, postgres, or redis.
directionstringoptionalThe direction to query logs for. Backward will return most recent logs first. Forward will start with the oldest logs in the time range.
endTimestringoptionalEnd time for log query (RFC3339 format). Defaults to the current time. The end time must be within the last 30 days.
hostarrayoptionalFilter request logs by their host. Wildcards and regex are supported.
instancearrayoptionalFilter logs by the instance they were emitted from. An instance is the id of a specific running server.
levelarrayoptionalFilter logs by their severity level. Wildcards and regex are supported.
limitnumberoptionalMaximum number of logs to return
methodarrayoptionalFilter request logs by their requests method. Wildcards and regex are supported.
patharrayoptionalFilter request logs by their path. Wildcards and regex are supported.
startTimestringoptionalStart time for log query (RFC3339 format). Defaults to 1 hour ago. The start time must be within the last 30 days.
statusCodearrayoptionalFilter request logs by their status code. Wildcards and regex are supported.
textarrayoptionalFilter by the text of the logs. Wildcards and regex are supported.
typearrayoptionalFilter 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

ParametersTypeDescription
includePreviewsbooleanoptionalWhether 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.

ParametersTypeDescription
postgresIdstringThe ID of the Postgres instance to query
sqlstringThe 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.

ParametersTypeDescription
ownerIDstringThe ID of the owner to select

This tool interacts with external entities.


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'.

ParametersTypeDescription
envVarsarrayThe list of environment variables to update or set for the service.
serviceIdstringThe ID of the service to update
replacebooleanoptionalWhether 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.

ParametersTypeDescription
serviceIdstringThe 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.

ParametersTypeDescription
serviceIdstringThe 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?

Manual installation

You can install the MCP server using:

Installation for

Related servers