Render MCP Server

- 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

-

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 asownerIDso existing callers of this deprecated tool keep working; new code should passworkspaceIdon each resource tool call instead.

get_selected_workspace- Get the currently selected workspace

Every resource tool also accepts an optionalworkspaceId. After the user confirms a workspace fromlist_workspaces, pass thatworkspaceIdon each related tool call. This keeps the target workspace explicit across MCP reconnects and transport-session changes. IfworkspaceIdis 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.

-

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:

- node
- python
- go
- rust
- ruby
- elixir
- docker

- starter
- standard
- pro
- pro_max
- pro_plus
- pro_ultra

- yes: Enable automatic deployments
- no: Disable automatic deployments

- oregon
- frankfurt
- singapore
- ohio
- virginia

create_static_site- Create a new static site in your Render account

- name: A unique name for your service (string, required)
- buildCommand: Command to build your app (string, required)
- repo: Repository containing source code (string, optional)
- branch: Repository branch to deploy (string, optional)
- autoDeploy: Whether to automatically deploy the service (string, optional). Defaults toyes. Accepted values:

- yes: Enable automatic deployments
- no: Disable automatic deployments

create_cron_job- Create a new cron job in your Render account

- name: A unique name for your cron job (string, required)
- 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:

- 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

- starter
- standard
- pro
- pro_max
- pro_plus
- pro_ultra

- yes: Enable automatic deployments
- no: Disable automatic deployments

- oregon
- frankfurt
- singapore
- ohio
- virginia

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)

- serviceId: The ID of the service to update (string, required)

- serviceId: The ID of the service to update (string, required)

- serviceId: The ID of the service to update (string, required)

-

list_deploys- List deployment history for a service

- serviceId: The ID of the service to get deployments for (string, required)

get_deploy- Get details about a specific deployment

- serviceId: The ID of the service (string, required)
- 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.

- serviceId: The ID of the service to deploy (string, required)
- clearCache: Whether to clear the build cache before deploying (boolean, optional). Defaults tofalse.

-

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)
- 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)
- limit: Maximum number of logs to return (number, 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)
- 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)

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

- AVG: Average CPU usage over time intervals
- MAX: Maximum CPU usage over time intervals
- MIN: Minimum CPU usage over time intervals

- host: Aggregate by request host
- statusCode: Aggregate by HTTP status code

-

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

- postgresId: The ID of the Postgres instance to query (string, required)
- sql: The SQL query to run (string, required)

list_postgres_instances- List all PostgreSQL databases in your Render account

get_postgres- Get details about a specific PostgreSQL database

- postgresId: The ID of the PostgreSQL database to retrieve (string, required)

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

- oregon
- frankfurt
- singapore
- ohio
- virginia

-

list_key_value- List all Key Value instances in your Render account

get_key_value- Get details about a specific Key Value instance

- keyValueId: The ID of the Key Value instance to retrieve (string, required)

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

- oregon
- frankfurt
- singapore
- ohio
- virginia

- 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

- 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

Expose the entire ArgoCD API to LLMs via MCP using just 2 auto-generated tools powered by the OpenAPI spec.

An MCP server for interacting with the Coolify API to manage servers and applications.

Integrate with the Laravel Forge API to manage servers and deployments using MCP-compliant tools.

Interact with Heroku Platform resources securely using the Heroku CLI. Requires the Heroku CLI and a valid API key.

Manage Koyeb resources like apps, services, and deployments using the Koyeb API.

MCP server exposing Spinnaker CD platform via Gate API for pipeline and deployment management

Create, build, deploy, and manage Netlify resources using natural language.

European cloud hosting. Use your favorite AI coding assistant to easily deploy and manage apps on Ploi Cloud.