Workspace-scoped Render actions for the DevOps host. Set the workspace first, then check status, pull logs, or trigger a deploy. Paste an API key; the official remote accepts Bearer for headless agents. Complements Cloudflare (DNS and cache). Do not create databases unless asked.
The token stays on the host agent. Other agents ask that agent. They never receive the vendor MCP.
Suggested host agents
A suggestion only. Nothing installs until you pick an agent.
- Kai
Publisher: Render
Credentials
Paste this on the host agent after install. Other agents never see it.
Create an API key in Render Account Settings. The official remote accepts it as a Bearer token.
Where to find thisMCP server
HTTPS only. Auth is a Bearer token stored as a secret on the host agent. Other agents never receive this endpoint or the token.
https://mcp.render.com/mcpSkills
Injected on the host agent only, matched to the active goal. At most two skills attach per turn.
Set the active Render workspace
Use Render MCP to list workspaces and set the one named in the brief before any other action. Every later call is scoped to that workspace.
Service and deploy status
Use Render MCP to report the named service state, latest deploy, and URL. If still building, say so and stop.
Read recent logs
Use Render MCP to pull recent error-level logs for the named service. Cite the service and deploy. Do not invent log lines.
Trigger a deploy
Use Render MCP to redeploy the named service after confirming the workspace. Return the deploy URL when done. Do not create a database or a new service unless asked.
Start building with AI agents
No credit card required • Free forever