MCP server for the Render Public API: all 207 endpoints plus workflow tools.
MCP server for the Render Public API: all 207 endpoints plus workflow tools.
A Model Context Protocol server for Render that exposes all 207 endpoints of the official Render Public API, plus a handful of higher-level tools for the workflows the raw API makes tedious.
services — 42metrics — 23postgres — 21workflows — 15env-groups — 13projects — 12webhooks — 11logs — 10static-sites — 9key-value — 8workspaces — 8deprecated — 8disks — 7Compare MCP servers by category, or browse hosted MCP servers if you prefer an endpoint over a local process.
Check the linked publisher documentation and your connected client's tool list. Names and availability can vary with the server version and account permissions.
| Tool | What it does |
|---|---|
| render_find_service | Resolves a service name — including a partial or approximate one — to a single Render service, returning its id plus close alternatives. |
| render_recent_logs | Fetches recent log lines for a service, resolving the service name and workspace id for you. |
| render_service_status | One-call triage for a service: its configuration, latest deploys, running instances and most recent error-level logs. |
| render_toolsets | Lists every Render toolset with its tool count and whether it is currently enabled. |
| render_wait_for_deploy | Polls a deploy until it reaches a terminal state (live, build_failed, update_failed, canceled, deactivated) or the timeout expires. |
{
"mcpServers": {
"render": {
"command": "npx",
"args": [
"-y",
"render-useful-mcp"
],
"env": {
"RENDER_API_KEY": "YOUR_RENDER_API_KEY",
"RENDER_WORKSPACE_ID": "tea_your_workspace_id"
}
}
}
}From the project documentation. Replace placeholders and example paths before connecting.
| Variable | Description | Required |
|---|---|---|
| RENDER_API_KEY | Declared in the maintainer’s client configuration. | Check documentation |
| RENDER_WORKSPACE_ID | Declared in the maintainer’s client configuration. | Optional |
Give your coding agent the full DevTools toolbox: traces, network, console, heap snapshots and Lighthouse.
Workers, KV, R2 and D1 by conversation — Cloudflare's official remote servers for building and observability.
Dashboards, Prometheus and Loki queries, incidents and alerts — observability by conversation.
Errors with full context — stack traces, issue triage and AI-powered root-cause analysis from Sentry's server.
Connect Flutter applications with AI coding assistants via the Model Context Protocol.
Enables natural language interaction with Splunk Enterprise and Cloud for searching data and managing resources.