Render MCP connector
Connect Render to Elaichi and Claude, ChatGPT, Cursor, Microsoft Copilot or any MCP client can list your services, look up deploy events, manage webhooks, blueprints and custom domains, all inside each person's own Render access with every call logged.
- Connects with an API key
- Free 14-day trial
- No credit card
Which Render blueprints changed in the last week?
Working in Render with Elaichi
-
List all Render workspaces
-
Get single Render workspace by ID
-
List all Render me
How to connect Render to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Render MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
Render MCP connector for Claude Code
-
1
In a terminal, run
claude mcp addwith the endpoint.https://api.elaichi.ai/mcp -
2
Start Claude Code and run
/mcp. -
3
Pick elaichi, then sign in and approve in the browser.
Terminal
$ claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
Use --scope project instead to share it with the repository through .mcp.json.
Render MCP connector for ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web. The plugin directory lives at chatgpt.com/plugins.
Render MCP connector for Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Render MCP connector for Microsoft Copilot
-
1
In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
-
2
Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
https://api.elaichi.ai/mcp -
3
Create a new connection, sign in and approve, then press Add to agent.
-
4
Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.
- Server URL
- https://api.elaichi.ai/mcp
- Authentication
- OAuth 2.0
- Type
- Dynamic discovery
Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.
Connect Render to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
What teams do with Render through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Render is logged.
-
Engineering
Check what a service is running
Ask which services live in a Render workspace and pull up one service's settings, region and connected repository without opening the Render dashboard.
-
Platform
Stand up a new service from chat
Describe the web service or background worker you need and have it created in Render, then adjust its settings later as the plan changes.
-
Platform
Keep blueprints current and synced
Review the blueprints defined in Render, see when each one last synced, and update or retire a blueprint once the infrastructure it describes has moved on.
-
Engineering
Point a custom domain at a service
Add a customer's domain to the right Render service and confirm it registered, or remove one when a contract ends.
-
Support
Piece together an incident timeline
Look up the Render event a customer is asking about and read the webhook events that fired around the same time to see what changed and when.
-
Security
Review who has access to Render
List the members of every Render workspace and check the roster against who is still on the team before an access review.
Try asking
- “Which Render blueprints changed in the last week?”
- “List webhooks configured across our Render workspaces.”
- “Show failed deploy events for the checkout service.”
What connecting Render gets you
6 screens from Elaichi, each doing one job for your Render account.
Ask Elaichi to work across your apps.
Which Render blueprints changed in the last week?
List webhooks configured across our Render workspaces.
Show failed deploy events for the checkout service.
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask about Render services in plain language.
Answers come from live Render workspaces, blueprints and deploy events.
Copy the endpoint
AI apps
Claude, ChatGPT, Cursor and Microsoft Copilot reach Render here.
One org MCP endpoint over OAuth, no SDK and no shared API key.
Tool catalog
144 Render tools ready without custom code.
Browse services, blueprints, webhooks and members with methods already wired up.
Toolboxes
Every team gets its own Render toolbox.
Platform, release and support teams each see a curated set of Render tools.
Shared connections
Teammates use Render accounts without seeing keys.
See who connected each Render account and which teams and members share it.
Audit log
Answer who deployed what on Render.
Every Render call is logged with time, actor, action, type and resource.
From answering questions to doing the work
A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations, collections and live dashboards come with the Black plan.
Render digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch workspaces
Render
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Jake Morgan
Approve Deny -
Post the digest
Render
Queued
Automations
A schedule turns Render events into a digest.
Fetch deploy events, group them, draft a digest, approve, post back to Render.
Render health
Refreshed 4 minutes ago · every 15 minutes · from the workspaces collection
Workspaces
1,284 ↓ 12%
Blueprints
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Workspaces created
Last 14 days
By team
Share of activity
Platform 34%
Release engineering 27%
Support 21%
Security 18%
Collections and dashboards
Render health arrives computed, not requested.
Four metrics, 14 days of services created, split by team, refreshed on schedule.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for Render
All three can connect Render to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.
| What to check | Elaichi | Zapier MCP | Composio |
|---|---|---|---|
| Where the AI connects |
One address for the whole organization.
https://api.elaichi.ai/mcp
|
A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Render tools | Allow or restrict single Render tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per Render call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | Free for one person; $15 per user per month on Gold. | 2 tasks per successful call. | Billed per tool call. |
Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
Render tools for your AI agents
144 tools are ready to call through Elaichi's MCP endpoint the moment you connect Render, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
Questions, answered
How do I connect Render to Claude?
Two steps. First connect Render in Elaichi by pasting a Render API key from your Render account settings, there is no client ID or secret to generate and no app to register on the Render side. Then in Claude open Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Sign in with your Elaichi login and Render appears in Claude.
Does Render work with ChatGPT and Cursor as well as Claude?
Yes. Once Render is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any other MCP client and Elaichi's own agent. You connect Render once and every client picks it up.
What can an AI agent actually do with my Render data?
With Render connected, an agent can list your workspaces, services, blueprints, custom domains and webhooks, pull up any one of them by ID, and create or update services, webhooks and custom domains when you ask. It can also read individual events and webhook events to work out what happened during a deploy or an incident. Because Render exposes a lot of actions, short concrete asks like "list the services in the production workspace" get better results than long paragraphs.
Does connecting Render give the AI access to every workspace?
No. Every request runs inside the Render access of the person who signed in, so the AI sees only the workspaces, services and members that person can already see in Render. Elaichi can narrow that further by restricting actions, but it can never grant anything the person does not have in Render.
Can I stop an agent from deleting or changing things in Render?
Yes. In Elaichi you can restrict any Render action on its own, for example deleting a service, removing a custom domain or changing a blueprint, while leaving the read-only ones in place. A restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT, Cursor, Microsoft Copilot or any other client cannot run it, whatever the prompt says.
What happens to a Render connection when someone leaves?
When a person is offboarded in Elaichi, their access to Render through every client ends at once. A Render connection they shared with a team keeps working for everyone else on that team. If you want Render gone entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client at the same time.
Does the Render MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Render is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.
Is Elaichi an alternative to Zapier MCP for Render?
Yes. Both let Claude, ChatGPT or Cursor use Render. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Render call.
How is Elaichi different from Composio for Render?
Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Render: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Render in front of your team
14 days of Black, no credit card. Connect it once and pick what each team can call.
When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.
Add one link to your AI app
The same link for everyone on your team.
https://api.elaichi.ai/mcp
ChatGPT
Claude
Cursor
Microsoft Copilot