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

  • No parameters required

• select_workspace - Select a workspace to use

  • ownerID: The ID of the workspace to use (string, required)

• get_selected_workspace - Get the currently selected workspace

  • No parameters required

Services

• 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
  • buildCommand: Command used to build your service (string, required)
  • startCommand: Command used to start your service (string, required)
  • repo: Repository containing source code (string, optional)
  • branch: Repository branch to deploy (string, optional)
  • plan: Plan for your service (string, optional). Accepted values:
    • starter
    • standard
    • pro
    • pro_max
    • pro_plus
    • pro_ultra
  • 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:
    • oregon
    • frankfurt
    • singapore
    • ohio
    • virginia
  • envVars: Environment variables array (array, optional)

• 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 to yes. Accepted values:
    • yes: Enable automatic deployments
    • no: Disable automatic deployments
  • publishPath: Directory containing built assets (string, optional)
  • envVars: Environment variables array (array, optional)

• 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
  • runtime: Runtime environment for your cron job (string, required). Accepted values:
    • node

... View full README on GitHub