home / mcp / render mcp server

Render MCP Server

An unofficial MCP server for Render to help developers ship code faster via Cline, Cursor, and Windsurf

Installation

Add the following to your MCP client configuration file.

Configuration

{
  "mcpServers": {
    "niyogi-render-mcp": {
      "command": "node",
      "args": [
        "bin/render-mcp.js",
        "start"
      ],
      "env": {
        "RENDER_API_KEY": "YOUR_API_KEY"
      }
    }
  }
}

You can run a dedicated MCP (Model Context Protocol) server that lets AI assistants manage and deploy services on Render.com. This server exposes a set of MCP endpoints you can invoke from your assistants to list, create, deploy, configure, and monitor your Render services from a single, centralized place.

How to use

Start by installing the MCP server, then configure it with your Render API key. Run the server and connect your AI assistant to use the Render MCP capabilities. You can list your Render services, get details for a specific service, deploy or create services, delete services, view deployment history, and manage environment variables or custom domains. Use these capabilities through your MCP-enabled assistant without needing to manually interact with Render’s dashboard.

How to install

Ensure you have Node.js installed on your machine. You can use Node 14+ or newer.

npm install -g @niyogi/render-mcp

Additional configuration and usage notes

Configure your MCP server with your Render API key to grant the server access to your Render account.

node bin/render-mcp.js configure --api-key=YOUR_API_KEY
```

Alternatively, run the configuration without the key and you will be prompted to enter it interactively.

Starting and managing the server

Once configured, start the MCP server in the terminal. The server will run locally and listen for commands from your MCP clients.

node bin/render-mcp.js start
```

If you installed the package globally, you can also use the shorter form to start the server.

Using with different MCP clients

Connect your AI assistant or client to Render MCP using the provided stdio-based command. You typically run the local server and configure your client to execute the start command as shown in the examples below.

render-mcp start
```

If you integrate with a different tool or environment, you may provide the same start command with its path and runtime as shown in your client’s configuration.

Example prompts you can use after connecting

- List all Render services - Show details for a specific service by ID - Deploy a service to Render - Create a new service from a template - Delete a service - Show deployment history for a service - Add or update environment variables for a service - Add a custom domain to a service

Security and best practices

Keep your Render API key secure. Store it in a protected environment variable or secret manager, and avoid exposing it in logs or command history. Only enable the MCP features you need and periodically rotate API keys.

Available tools

list_services

Return a list of all services in your Render account.

get_service_details

Retrieve detailed information for a specific Render service by ID.

deploy_service

Deploy a service to Render, triggering a new deployment for the selected service.

create_service

Create a new Render service from a template or configuration.

delete_service

Remove a Render service from your account.

get_deployment_history

Fetch the deployment history for a specific service.

manage_env_vars

Add, update, or remove environment variables for a Render service.

manage_custom_domains

Attach or manage custom domains for a Render service.