Claude + Render: What the Integration Can (and Can't) Do in 2026
Yes — Render ships an official MCP server for Claude. To be clear on which Render this is: render.com, the cloud application-hosting platform where you deploy web services, static sites, cron jobs, and databases (not a rendering or video tool). Render maintains a first-party MCP server (repo: render-oss/render-mcp-server) with a hosted endpoint at https://mcp.render.com/mcp, authenticated with your Render API key. Wire it up and Claude can create and manage services, check deploys, read logs and metrics, and query your Render Postgres from a chat. The catch is the one every Claude MCP setup carries: it only works inside a conversation you start — there are no triggers, and nothing runs while you’re away.
Here’s exactly what the integration does, how to turn it on, where the limits bite, and what to use if you want Render work that runs on its own.
What Render’s MCP server does
Render’s MCP server connects Claude directly to your Render workspace, exposing infrastructure operations as tools you drive with natural language.
In practice, it lets Claude:
- List and inspect your workspace — see workspaces, services, sites, cron jobs, and databases.
- Create and manage infra — spin up and update web services, static sites, cron jobs, and databases.
- Watch deploys and logs — check deploy status and pull logs to help debug a failing build or a crashing service.
- Read metrics and query Postgres — pull service metrics with
get_metrics, and run read queries against your Render Postgres withquery_render_postgres.
Everyday wins: “why did my last deploy fail?”, “show me the error logs for this service,” “what’s the CPU on my web service right now,” “create a cron job that runs this script nightly.” All without leaving Claude. Render recommends the hosted server (https://mcp.render.com/mcp) over running it locally, so it auto-updates.
How to set it up
Setup is a custom MCP server, and Render’s documented flow is API-key based — which works cleanly in Claude Code and Claude Desktop:
- Create a Render API key in your Render Account Settings.
- Add Render’s hosted MCP server (
https://mcp.render.com/mcp) as a custom connector in Claude Code or Claude Desktop, passing your API key per Render’s setup docs. - In a chat, ask Claude to list your services or check a deploy — it hits Render’s MCP server on your behalf.
Two honest notes. First, Render’s key is broadly scoped across the workspaces and services your account can reach — treat it as a sensitive credential. Second, the documented auth is an API key, which is ideal for Claude Code and Desktop; the claude.ai web custom-connector UI generally prefers OAuth, so don’t assume the API-key header path works one-click in the browser client — use Claude Code or Desktop for the documented flow. (Third-party wrappers like Composio also exist, but the first-party Render server is the one to use.)
The limits that actually matter
The MCP server is great at pulling Render into a conversation. But its shape is “an SRE you operate,” not “an agent that watches.” Three limits define it:
- No triggers, no monitoring. The server only works inside a conversation you start. There’s no “alert me when a deploy fails and restart it” or “watch this service and page me when error rate spikes.” Nothing fires on a Render event — you have to be there, prompting.
- Conversation-only. Claude inspects and acts when you ask; it doesn’t sit watching your deploys or logs and responding on its own. Close the chat and nothing continues.
- Laptop-bound for anything scheduled. The closest thing to “running on its own” is Claude Cowork’s scheduled tasks, which fire on a fixed clock, not on inbox events. That’s not an always-on, event-driven ops agent.
So Claude is excellent for “help me debug this deploy right now” and not built for “watch my services and respond the moment something breaks.”
If you want Render work that runs on its own: Carly
The moment you want something to happen around Render without you in the chat — react to a failed deploy, post a status update when a service goes down, run a check on a schedule, tie an infra event to the rest of your stack — you’ve crossed past what Claude’s MCP server is for.
That’s where Carly fits. Carly is an AI executive assistant built to act on triggers, not just answer in a chat:
- Fires on events and schedules, 24/7, in the cloud — react to a Render webhook (deploy succeeded/failed, service event) or run a scheduled health check; your laptop doesn’t need to be awake.
- Connects Render to the rest of your stack — when a deploy fails, post to Slack, open an issue, and email the on-call — in one workflow that also touches your calendar and tasks.
- Actually sends and updates — drafts and sends email (Gmail and Outlook) with attachments, files and labels, manages tasks, and records meetings.
- Builds the workflow for you — tell it “when a Render deploy fails, message the team and open a ticket” in plain English; it interviews you, then builds it with you. No prompt engineering.
Carly can drive Render through its public REST API with your own API key (services, deploys, databases, env) and catch Render’s webhooks as triggers. AI agents start at $35/month, and steps in a workflow that don’t use AI run free and unlimited. Carly connects to 200+ tools across 40+ categories — see integrations. Carly natively integrates with Render.
Claude’s Render MCP vs Carly
| Claude (Render MCP) | Carly | |
|---|---|---|
| List / inspect services | Yes | Yes |
| Create & manage infra | Yes | Yes (via API key) |
| Check deploys & read logs | Yes | Yes |
| Acts on triggers / webhooks | No | Yes |
| Reacts to a failed deploy on its own | No | Yes |
| Works while laptop is closed | No | Yes (cloud) |
| Sends alerts / email as part of the flow | No (Gmail draft-only) | Yes (Gmail + Outlook) |
| Pricing | Pro $20 / Max $100–$200 | AI agents from $35/mo |
Claude’s MCP server is a strong Render console inside a chat. Carly is a teammate that reacts to Render events and drives the follow-on work as they happen.
Frequently Asked Questions
Does Claude work with Render?
Yes. Render ships an official first-party MCP server (hosted at https://mcp.render.com/mcp, repo render-oss/render-mcp-server) that connects Claude to your Render workspace — Claude can list and create services, check deploys, read logs and metrics, and query Render Postgres. You add it as a custom MCP server with your Render API key; the documented flow works in Claude Code and Claude Desktop, and like all MCP setups it only works inside a conversation you start.
Does the Render connector work in claude.ai on the web?
Render’s documented auth is an API key, which is ideal for Claude Code and Claude Desktop. The claude.ai web custom-connector UI generally prefers OAuth, so don’t assume the API-key header path works one-click in the browser — use Claude Code or Desktop for the documented setup.
Can Claude react to a failed deploy automatically?
No. The MCP server only works inside a conversation you start — there are no event triggers, so Claude won’t respond to a failed deploy or a service going down on its own. For automatic, trigger-based Render work, you need an agent platform like Carly, which catches Render webhooks and runs on a schedule 24/7.
How do I connect Claude to Render?
Create a Render API key in Account Settings, then add the hosted MCP server (https://mcp.render.com/mcp) as a custom connector in Claude Code or Claude Desktop per Render’s docs. The key is broadly scoped across your workspaces, so treat it as sensitive.
More: Claude connectors · Claude + Vercel · Claude + Netlify · Claude + GitHub · Can Claude send emails · Claude vs Carly
Ready to automate your busywork?
Carly schedules, researches, and briefs you—so you can focus on what matters.
See what people say
"Before Carly, I relied on a Calendly link, but the whole process felt impersonal and not very professional. Carly changed that by handling all the back-and-forth, so I'm no longer stuck in endless email threads trying to line up schedules.
Now Carly reaches out to candidates, shares my real-time availability, lets them pick a slot, then sends a Zoom link and drops it straight into my calendar. She sends reminders to both of us before each call, which has significantly reduced no-shows and last-minute confusion.
On top of scheduling, Carly acts like a full executive assistant, sending me my schedule the night before so I can prepare for each call. It reminds me of the old x.ai assistant, but Carly is noticeably smarter, faster, and better suited to my healthcare recruitment business."
