Agenten stärken
Installation vom Herausgeber. Kein PlugMCP-Endpunkt.
Host a copy with our keys and logs.
Noch kein paketiertes Release in der Registry. Folgen Sie der README des Repositorys.
Remote-URL oder ein Befehl auf Ihrem Rechner? Worin sich die beiden Installationen unterscheiden
Auf PlugMCP ausführen
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
StartenVom Herausgeber
Deploy to Render.com directly through AI assistants.
This MCP (Model Context Protocol) server allows AI assistants like Claude to interact with the Render API, enabling deployment and management of services on Render.com.
An unofficial MCP server for Render to help developers ship code faster via Cline, Cursor, and Windsurf
This server covers everything Render's official MCP server does plus mutating operations their server intentionally omits (triggering deploys, deleting resources, managing custom domains, restarting, and cancelling deploys).
Services
create_service plus typed create_web_service,
create_static_site, and create_cron_jobDeploys
Workspaces
ownerId each callObservability
list_logs) and enumerate log label valuesget_metrics): CPU, memory, HTTP requests/latency,
bandwidth, instance count, active connectionsDatastores
query_render_postgres)Note on
query_render_postgres: this tool connects to your database using thepgdriver and enforces read-only access (single statement,SELECT/WITH/EXPLAIN/SHOWonly, run inside aREAD ONLYtransaction). Runnpm installafter installing the package to ensure thepgdependency is present.
npm install -g @niyogi/render-mcp
node bin/render-mcp.js configure --api-key=YOUR_API_KEY
Alternatively, you can run node bin/render-mcp.js configure without the --api-key flag to be prompted for your API key.
node bin/render-mcp.js start
node bin/render-mcp.js config
node bin/render-mcp.js doctor
Note: If you've installed the package globally, you can also use the shorter commands:
render-mcp start
render-mcp config
render-mcp doctor
The quickest way is the claude mcp add CLI, which registers the server via npx
(no global install needed):
claude mcp add render -e RENDER_API_KEY=YOUR_API_KEY -- npx -y @niyogi/render-mcp start
By default this adds the server to the current project. Use a scope flag to change that:
-s user — available across all your projects-s project — shared with your team via a checked-in .mcp.json-s local (default) — just this project, only for youAlternatively, add it manually to your MCP config (.mcp.json in the project root,
or ~/.claude.json for user scope):
{
"mcpServers": {
"render": {
"command": "npx",
"args": ["-y", "@niyogi/render-mcp", "start"],
"env": {
"RENDER_API_KEY": "YOUR_API_KEY"
}
}
}
}
Instead of passing the key via env, you can store it once with
npx @niyogi/render-mcp configure (saved to ~/.render-mcp/config.json) and omit
the env block.
Then verify the connection inside Claude Code with the /mcp command — render
should appear as connected and its tools listed.
Add the following to your Cline MCP settings file:
{
"mcpServers": {
"render": {
"command": "node",
"args": ["/path/to/render-mcp/bin/render-mcp.js", "start"],
"env": {
"RENDER_API_KEY": "your-render-api-key"
},
"disabled": false,
"autoApprove": []
}
}
}
Restart Cline for the changes to take effect
You can now interact with Render through Claude:
Claude, please deploy my web service to Render
Install the render-mcp package:
npm install -g @niyogi/render-mcp
Configure your API key:
node bin/render-mcp.js configure --api-key=YOUR_API_KEY
Start the MCP server in a separate terminal:
node bin/render-mcp.js start
In Windsurf/Cursor settings, add the Render MCP server:
You can now use the Render commands in your AI assistant
For custom applications using Claude's API directly:
Ensure the render-mcp server is running:
node bin/render-mcp.js start
In your application, when sending messages to Claude via the API, include the MCP server connections in your request:
{
"mcpConnections": [
{
"name": "render",
"transport": {
"type": "stdio",
"command": "node",
"args": ["/path/to/render-mcp/bin/render-mcp.js", "start"]
}
}
]
}
Claude will now be able to interact with your Render MCP server
Here are some example prompts you can use with Claude once the MCP server is connected:
git clone https://github.com/niyogi/render-mcp.git
cd render-mcp
npm install
npm run build
npm test
MIT
An unofficial MCP server for Render to help developers ship code faster via Cline, Cursor, and Windsurf
Tools
Noch keine Tool-Liste. Remote-Server erhalten eine nach dem ersten Health-Check.
FAQ
Kopieren Sie auf dieser Seite die stdio-Konfiguration für Cursor, Claude Desktop, Claude Code oder VS Code. Sie nutzt die Installation des Herausgebers, keinen PlugMCP-Proxy.
In diesem Eintrag ist keine erforderliche Umgebungsvariable aufgeführt.
Render läuft lokal über stdio.
Zuletzt geprüft: 2026-10-28. An unofficial MCP server for Render to help developers ship code faster via Cline, Cursor, and Windsurf
