render

This Render MCP Server exposes a set of tools that let you interact with your Render resources from an LLM. The server organizes capabilities into logical groups such as Workspaces, Services, Deployments, and Logs. You can list workspaces, select a workspace, and query the currently selected workspace. For services, you can list, inspect, create web services and static sites, manage cron jobs, and update environment variables. Deployments and logs endpoints let you review deployment histories and fetch logs with filters like resource type, log level, and path. There are specialized actions for creating and managing resources directly from prompts, enabling end-to-end workflows inside an LLM-driven assistant. The included tool definitions describe required parameters for each action so you can craft precise prompts to perform common tasks like deploying a new web service, monitoring deployment status, or querying Postgres data via the MCP server.

Prerequisites:

• Node.js (12.x or newer) and npm/yarn installed on your machine
• Basic understanding of MCP (Model Context Protocol) and how to issue tool calls from an LLM

Step 1: Install the MCP server package (example package name used in this repository)

• npm install -g render-mcp-server (or follow the project’s preferred installation method)

Step 2: Prepare configuration

• Create a config file or rely on environment variables as described in the mcp_config section
• Ensure you have a Render API key and account ID if you plan to operate on real Render resources

Step 3: Run the MCP server

• npx render-mcp-server (or node server.js if running from source)
• If running from source, ensure your working directory contains server.js (or the supplied entry point) and all dependencies are installed

Step 4: Connect your client (LLM) to the MCP server

• Point your client to the MCP server’s host and port as configured in your deployment
• Use the documented MCP endpoints to perform actions via prompts

Tips and common considerations:

• Always start with a minimal workspace/service query to verify authentication and permissions
• Use the env section in the mcp_config to pass API keys, account IDs, and other sensitive data securely
• When creating resources (e.g., web services or cron jobs), double-check runtime and region defaults to avoid deployment delays
• If you encounter rate limits or API errors from Render, increase logging verbosity and review API quotas in your account
• For post-deployment tasks, use list_deploys and get_deploy to monitor deployment status and diagnose failures quickly
• The MCP tool definitions include explicit parameter names; craft prompts that map directly to those parameters to reduce ambiguity