Render MCP Server

Overview

The Render MCP Server is a Model Context Protocol (MCP)

server that allows you to interact with your Render resources via LLMs.

Getting Started

Get started with the MCP server by following the official docs: https://render.com/docs/mcp-server

Use Cases

• Creating and managing web services, static sites, cron jobs, and databases on Render
• Monitoring application logs and deployment status to help troubleshoot issues
• Monitoring service performance metrics for debugging, capacity planning, and optimization
• Querying your Postgres databases directly inside an LLM

Feedback

Please leave feedback via

filing a GitHub issue if you have any

feature requests, bug reports, suggestions, comments, or concerns.

Tools

Workspaces

• list_workspaces - List the workspaces that you have access to

• select_workspace - Select a workspace to use

existing callers of this deprecated tool keep working; new code should pass `workspaceId`

on each resource tool call instead.

• get_selected_workspace - Get the currently selected workspace
  • No parameters required

Every resource tool also accepts an optional `workspaceId`. After the user confirms a workspace from

`list_workspaces`, pass that `workspaceId` on each related tool call. This keeps the target workspace

explicit across MCP reconnects and transport-session changes. If `workspaceId` is omitted, the server

temporarily falls back to the workspace selected in the current MCP session. That implicit

session-based behavior is deprecated and is scheduled for removal.

Services

• list_services - List all services in your Render account

• get_service - Get details about a specific service

• create_web_service - Create a new web service in your Render account

• create_static_site - Create a new static site in your Render account

• create_cron_job - Create a new cron job in your Render account

• update_environment_variables - Update all environment variables for a service
  • `serviceId`: The ID of the service to update (string, required)
  • `envVars`: Complete list of environment variables (array, required)

• 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).

• 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).

• 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).

Deployments

• list_deploys - List deployment history for a service

• get_deploy - Get details about a specific deployment

• 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.
  • `serviceId`: The ID of the service to deploy (string, required)
  • `clearCache`: Whether to clear the build cache before deploying (boolean, optional). Defaults to `false`.

Logs

• list_logs - List logs matching the provided filters

• 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)
  • `resource`: Filter by 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)
  • `startTime`: Start time for log query (RFC3339 format) (string, optional)
  • `endTime`: End time for log query (RFC3339 format) (string, optional)
  • `direction`: The direction to query logs for (string, optional)

Metrics

• 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)
  • `startTime`: 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 (string, optional)
  • `endTime`: 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 (string, optional)
  • `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:
    • `host`: Aggregate by request host
    • `statusCode`: Aggregate by HTTP status code
  • `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)

Postgres Databases

• query_render_postgres - Run a read-only SQL query against a Render-hosted Postgres database

• list_postgres_instances - List all PostgreSQL databases in your Render account

• get_postgres - Get details about a specific PostgreSQL database

• create_postgres - Create a new PostgreSQL database
  • `name`: Name of the PostgreSQL database (string, required)
  • `plan`: Pricing plan for the database (string, required). Accepted values:
    • `free`
    • `basic_256mb`
    • `basic_1gb`
    • `basic_4gb`
    • `pro_4gb`
    • `pro_8gb`
    • `pro_16gb`
    • `pro_32gb`
    • `pro_64gb`
    • `pro_128gb`
    • `pro_192gb`
    • `pro_256gb`
    • `pro_384gb`
    • `pro_512gb`
    • `accelerated_16gb`
    • `accelerated_32gb`
    • `accelerated_64gb`
    • `accelerated_128gb`
    • `accelerated_256gb`
    • `accelerated_384gb`
    • `accelerated_512gb`
    • `accelerated_768gb`
    • `accelerated_1024gb`
  • `region`: Region for deployment (string, optional). Accepted values:
    • `oregon`
    • `frankfurt`
    • `singapore`
    • `ohio`
    • `virginia`
  • `version`: PostgreSQL version to use (e.g., 14, 15) (number, optional)
  • `diskSizeGb`: Database capacity in GB (number, optional)

Key Value instances

• list_key_value - List all Key Value instances in your Render account

• get_key_value - Get details about a specific Key Value instance

• create_key_value - Create a new Key Value instance
  • `name`: Name of the Key Value instance (string, required)
  • `plan`: Pricing plan for the Key Value instance (string, required). Accepted values:
    • `free`
    • `starter`
    • `standard`
    • `pro`
    • `pro_plus`
  • `region`: Region for deployment (string, optional). Accepted values:
    • `oregon`
    • `frankfurt`
    • `singapore`
    • `ohio`
    • `virginia`
  • `maxmemoryPolicy`: Eviction policy for the Key Value store (string, optional). Accepted values:
    • `noeviction`: No eviction policy (may cause memory errors)
    • `allkeys_lfu`: Evict least frequently used keys from all keys
    • `allkeys_lru`: Evict least recently used keys from all keys
    • `allkeys_random`: Evict random keys from all keys
    • `volatile_lfu`: Evict least frequently used keys from keys with expiration
    • `volatile_lru`: Evict least recently used keys from keys with expiration
    • `volatile_random`: Evict random keys from keys with expiration
    • `volatile_ttl`: Evict keys with shortest time to live from keys with expiration
  • `persistenceMode`: Data persistence behavior for the Key Value store (string, optional). Accepted values:
    • `journal_snapshot`: Append all writes to a journal and periodically save a snapshot to disk
    • `snapshot`: Periodically save a snapshot to disk
    • `off`: Disable persistence completely to prioritize write performance