Skip to content

CI

Render MCP connector

Connect Render to Elaichi and Claude, ChatGPT, Cursor 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.

  • How it connects. Connects with an API key. The credential goes into a vault nobody reads back.

  • One address. https://api.elaichi.ai/mcp, the same for every user.

  • Their own access. An agent never gets more than the person it acts for.

How to connect

How to connect Render to Claude, ChatGPT or Cursor

Two steps, about a minute.

1

In Elaichi

Connect Render once

  1. Open Connections, choose Add connection, and pick Render.

  2. Optionally set Share with to give a team access, then press Connect.

  3. Paste a Render API key. One person generates a token in Render and pastes it once. Everyone else works through Share with, and never sees it.

The credential is vaulted. Nobody reads it back, not even the AI.

Add connection

Choose a connector.

render
Render
1Password
360learning
7shifts
Acquire
Ada
2

In your AI client

Point it at one endpoint

Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.

Connect Render to Claude

  1. 1

    Open Customize, then Connectors.

  2. 2

    Press Add.

  3. 3

    Name it, paste the MCP server URL, then Continue.

    https://api.elaichi.ai/mcp
  4. 4

    Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

Connect Render to ChatGPT

  1. 1

    Open Plugins, then press the + button.

  2. 2

    Name it and paste the endpoint into Server URL.

    https://api.elaichi.ai/mcp
  3. 3

    Leave Authentication on OAuth, then tick the risk acknowledgement.

  4. 4

    Press Create, then sign in and approve.

Works on the web today. The plugin directory lives at chatgpt.com/plugins.

Connect Render to Cursor

  1. 1

    Open ~/.cursor/mcp.json.

  2. 2

    Add the endpoint under mcpServers.

    https://api.elaichi.ai/mcp
  3. 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.

Connect Render to any MCP client

  1. 1

    Add the endpoint as a remote MCP server.

    https://api.elaichi.ai/mcp
  2. 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.

Use cases

What teams do with Render through Elaichi

Every one of these runs inside the access the person already has, and lands in the same audit log.

  • 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.”

See all 144 Render tools below

AI tools

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.

See it in Elaichi

What connecting Render gets you

6 screens from the product, each doing one job for your Render account.

The agent

Ask about Render services in plain language.

Answers come from live Render workspaces, blueprints and deploy events.

  • workspaces
  • blueprints
  • webhooks
  • events

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 or Cursor

MCP clients

Claude, ChatGPT and Cursor reach Render here.

One org MCP endpoint over OAuth, no SDK and no shared API key.

ElaichiMCP clients
Claude ChatGPT Cursor

Copy the endpoint

https://api.elaichi.ai/mcp
Client Connected by Status Last used
Claude
E

Emma Laurent

• Connected 4 minutes ago
Cursor
S

Sofia Ricci

• Connected 2 hours ago
ChatGPT
C

Clara Nowak

• Connected Yesterday

Tool catalog

144 Render tools ready without custom code.

Browse services, blueprints, webhooks and members with methods already wired up.

  • List all Render workspaces
  • Get single Render workspace by ID
  • List all Render me
  • List all Render workspace members
ElaichiTools
Tool Action Description
List all Render workspaces List List workspaces accessible by your API key in Render, filtered by name or owner email. Returns owner details including id, name, email, twoFactorAuthEnabled, and type, along with a cursor for pagination.
Get single Render workspace by ID Get Get workspace by ownerId in Render. Provide ownerId which can be a workspace ID starting with 'tea-' or a user ID starting with 'own-'. Returns the workspace details or user's default workspace.
List all Render me List Get the authenticated user in Render. Returns email and name of the user associated with the provided API key.
List all Render workspace members List List workspace members for the workspace with owner_id in Render. Returns userId, name, email, status, role, and mfaEnabled for each member.
Get single Render event by ID Get Get details of a specific event in Render by id. Returns event id, timestamp, serviceId, type, and details describing the event configuration or status.

Toolboxes

Every team gets its own Render toolbox.

Platform, release and support teams each see a curated set of Render tools.

  • Platform
  • Release engineering
  • Support
  • Security
ElaichiToolboxes
Name Source template Tools Created

Platform toolbox

Render · workspaces and members

Render starter 18 Mar 4, 2026

Release engineering toolbox

Render · blueprints and deploys

9 Mar 2, 2026

Support toolbox

Render · events and service status

24 Feb 27, 2026

Security toolbox

Render · webhooks and access

Render starter 6 Feb 19, 2026

Data toolbox

Render · deploy events and metrics

31 Jan 30, 2026

QA toolbox

Render · preview environments and builds

12 Jan 22, 2026

Shared connections

Teammates use Render accounts without seeing keys.

See who connected each Render account and which teams and members share it.

  • Platform
  • Release engineering
  • Support
  • Security
ElaichiConnections
Connection Scope Status Access
RE

Render (Platform)

Connected by Emma Laurent

Personal • Active 1 team · 6 members
RE

Render (Release engineering)

Connected by James Whitfield

Organization • Active 3 teams · 24 members
RE

Render (Support)

Connected by Sofia Ricci

Organization • Active 2 teams · 11 members
RE

Render (Security)

Connected by Daniel Ortega

Personal • Needs re-auth 1 team · 3 members
RE

Render (Staging)

Connected by Clara Nowak

Personal • Active Not shared
RE

Render (Production)

Connected by Michael Brennan

Personal • Active 2 teams · 9 members

Audit log

Answer who deployed what on Render.

Every Render call is logged with time, actor, action, type and resource.

  • When
  • Who
  • What happened
  • Type
ElaichiAudit log
When Who What happened Type

2 minutes ago

Mar 6, 2026, 3:10 PM

E

Emma Laurent

[email protected]

Restriction Created Access

8 minutes ago

Mar 6, 2026, 3:04 PM

J

James Whitfield

[email protected]

Restriction Updated Access

14 minutes ago

Mar 6, 2026, 2:58 PM

S

Sofia Ricci

[email protected]

Role Assigned Access

20 minutes ago

Mar 6, 2026, 2:52 PM

D

Daniel Ortega

[email protected]

Render Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM

C

Clara Nowak

[email protected]

Render Workspaces Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM

M

Michael Brennan

[email protected]

Render Workspaces List Toolbox

Launching soon

From answering questions to doing the work

A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.

Automations

A schedule turns Render events into a digest.

Fetch deploy events, group them, draft a digest, approve, post back to Render.

Render digest

Run 418 · started 2 minutes ago · on behalf of Emma Laurent

  1. Schedule

    Every weekday at 08:00

    0.2s
  2. Fetch workspaces

    Render

    1.4s
  3. Group by owner

    Transform

    0.1s
  4. Draft the digest

    Agent step

    Ran with 4 tools, returned a structured summary

    6.2s
  5. Approve the digest

    Needs approval

    Assigned to Michael Brennan

    Approve
  6. Post the digest

    Render

    Queued

Collections and dashboards

Render health arrives computed, not requested.

Four metrics, 14 days of services created, split by team, refreshed on schedule.

Render health

Refreshed 4 minutes ago · every 15 minutes · from the workspaces collection

Live

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%

FAQ

Frequently asked questions

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, 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 hiding actions or resources, but it can never grant anything the person does not have in Render.

Can my team share one Render connection?

Yes. One person connects Render in Elaichi and shares the connection with a team, and nobody else ever handles the Render API key. Each teammate still signs in to Elaichi as themselves, so the audit log records exactly who asked for what in Render.

Can I stop an agent from deleting or changing things in Render?

Yes. In Elaichi you can block 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 blocked action is never shown to Claude, ChatGPT, Cursor or any other client, so no prompt can reach it.

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 and every other client at the same time.

Put Render in front of your team

Fourteen days on Gold, no credit card. Connect it once and pick what each team can call.