Render Useful MCP runs on your own machine — the client starts it, so there is no endpoint to ping. 79 installs a week from npm. Last commit 17 Sep 2026.
MCP server for the Render Public API: all 207 endpoints plus workflow tools.
Today is the operative word: we check Render Useful MCP every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add render-useful-mcp -e 'RENDER_API_KEY=<RENDER_API_KEY>' -- npx -y render-useful-mcp
{
"mcpServers": {
"render-useful-mcp": {
"command": "npx",
"args": [
"-y",
"render-useful-mcp"
],
"env": {
"RENDER_API_KEY": "<RENDER_API_KEY>"
}
}
}
}
[mcp_servers.render-useful-mcp]
command = "npx"
args = ["-y", "render-useful-mcp"]
env = { RENDER_API_KEY = "<RENDER_API_KEY>" }
{
"mcpServers": {
"render-useful-mcp": {
"command": "npx",
"args": [
"-y",
"render-useful-mcp"
],
"env": {
"RENDER_API_KEY": "<RENDER_API_KEY>"
}
}
}
}
{
"servers": {
"render-useful-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"render-useful-mcp"
],
"env": {
"RENDER_API_KEY": "<RENDER_API_KEY>"
}
}
}
}
Put your own value in place of
<RENDER_API_KEY> (Render API key, created at https://dashboard.render.com/u/settings#api-keys).
The author’s registry entry marks it as required.
Optional settings from the registry entry, left out of the block above:
RENDER_WORKSPACE_ID (Default workspace, applied wherever a tool needs an ownerId and the caller omitted one), RENDER_MCP_TOOLSETS (Comma-separated toolsets to expose, or 'all'. Defaults to all 17 toolsets), RENDER_MCP_READ_ONLY (Expose only non-mutating tools), RENDER_MCP_DYNAMIC_TOOLSETS (Registers the render_toolsets tool, which reports which toolsets exist and which are enabled).
MCP server for the @agentutility browser-workflow cluster — pay-per-call x402 tools, no API keys…
Free public MCP for AI agents — 193 tools, 44 workflows. No API key.
MCP server for HaloPSA — clients, tickets, and PSA workflows via the HaloPSA REST API.
MCP server for HaloPSA — clients, tickets, and PSA workflows via the HaloPSA REST API.
MCP server for the Codabench REST API — drives a full ML-benchmark participant workflow.
MCP server for your apps' tools and custom tools, plus hosted AI agents and approval-gated workflows
New Relic MCP server with 55 tools for APM, alerts, dashboards, synthetics, workflows, and more.
MCP server for the phlow agent runtime: bounded planner-coder-reviewer agent workflows.
Answers built from our own checks of this server.