# 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.

Source: https://elaichi.ai/connectors/render/

## Facts

| | |
| --- | --- |
| Application | Render |
| Category | CI |
| AI tools | 144 |
| Authentication | Connects with an API key |
| Bring your own OAuth app | No |
| MCP endpoint | https://api.elaichi.ai/mcp |
| Works with | Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client, and the Elaichi Agent |
| Tools advertised by name | No. Connected tools are never listed one by one, however few there are. The endpoint advertises `search_tools` and `execute_tool` instead |

## What you can ask once Render is connected

- Which Render blueprints changed in the last week?
- List webhooks configured across our Render workspaces.
- Show failed deploy events for the checkout service.

## Connect Render in Elaichi

This happens once for the organization, before any client is involved.

1. Open Connections, choose Add connection, and pick Render.
2. Optionally set Share with, 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.

Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which Render tools are exposed, rename them, or freeze arguments before anyone points a client at it.

## Render MCP connector for Claude

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

1. Open Customize, then Connectors.
2. Press Add.
3. Name it, paste the MCP server URL, then Continue.
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

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

1. In a terminal, run `claude mcp add` with the endpoint.
2. Start Claude Code and run `/mcp`.
3. Pick elaichi, then sign in and approve in the browser.

```bash
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

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

1. Open Plugins, then press the + button.
2. Name it and paste the endpoint into Server URL.
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

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

1. Open `~/.cursor/mcp.json`.
2. Add the endpoint under `mcpServers`.
3. Reload Cursor, then sign in and approve.

Set up per machine, so repeat it on each computer you work from.

## Render MCP connector for Microsoft Copilot

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

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

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

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

1. Add the endpoint as a remote MCP server.
2. Sign in and approve.

The Elaichi Agent already has these tools, with nothing to set up.

## What the consent screen decides

Every scope the client asks for starts ticked except "Delete things", which you tick yourself. Calling a Render tool needs "Use your connected apps". Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Think hard before granting Use your connected apps, which can also delete in connected apps and cannot be undone.

## What teams do with Render through Elaichi

### Check what a service is running

Engineering. Ask which services live in a Render workspace and pull up one service's settings, region and connected repository without opening the Render dashboard.

### Stand up a new service from chat

Platform. Describe the web service or background worker you need and have it created in Render, then adjust its settings later as the plan changes.

### Keep blueprints current and synced

Platform. 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.

### Point a custom domain at a service

Engineering. Add a customer's domain to the right Render service and confirm it registered, or remove one when a contract ends.

### Piece together an incident timeline

Support. 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.

### Review who has access to Render

Security. List the members of every Render workspace and check the roster against who is still on the team before an access review.

## 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. Endpoint: 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](https://docs.zapier.com/mcp/get-started/quickstart), [security](https://docs.zapier.com/mcp/manage/security), [usage](https://docs.zapier.com/mcp/features/usage); Composio [docs](https://docs.composio.dev/docs/composio-connect), [gateway](https://composio.dev/mcp-gateway), [enterprise](https://composio.dev/enterprise), [pricing](https://composio.dev/pricing). Checked September 2026.

Longer take: [Zapier MCP alternative](/blog/zapier-mcp-alternative/) and [when you don't need an MCP gateway](/blog/when-you-dont-need-an-mcp-gateway/).

## 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, 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 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 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.

## All 144 Render tools

Every tool below is callable through https://api.elaichi.ai/mcp once Render is connected, subject to the toolbox it is in and the restrictions on the caller.

- **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.
- **List all Render webhooks** (List). List webhooks with optional ownerId filter in Render. Returns webhook objects including id, url, name, secret, enabled status, and eventFilter, along with a cursor for pagination.
- **Get single Render webhook by ID** (Get). Get webhook by id in Render. Returns id, url, name, secret, enabled status, and eventFilter which lists event types triggering the webhook.
- **Create a Render webhook** (Create). Create a webhook in Render with enabled status. Returns id, url, name, secret, enabled, and eventFilter fields in the response.
- **Update a Render webhook by ID** (Update). Update a webhook by id in Render. Returns id, url, name, secret, enabled status, and eventFilter array indicating event types triggering the webhook.
- **Delete a Render webhook by ID** (Delete). Delete a webhook by id in Render. Returns status 204 on success. Possible error responses include 401 for authorization issues, 404 if webhook not found, 429 for rate limit exceeded, 500 for server error, and 503 if server unavailable. Response errors include id and message fields.
- **List all Render webhook events** (List). List webhook events for webhook with id in Render. Returns webhookEvent objects including id, eventId, eventType, sentAt, statusCode, responseBody, and error fields.
- **List all Render blueprints** (List). List blueprints filtered by ownerId in Render. Returns blueprint objects with id, name, status, autoSync, repo, branch, and lastSync fields. Requires ownerId if filtering by workspace.
- **Get single Render blueprint by ID** (Get). Retrieve blueprint by id in Render. Returns id, name, status, autoSync, repo, branch, lastSync, and resources with their id, name, and type.
- **Update a Render blueprint by ID** (Update). Update blueprint with id in Render. Returns id, name, status (created, paused, in_sync, syncing, error), autoSync, repo, branch, and lastSync fields in response.
- **Delete a Render blueprint by ID** (Delete). Disconnect blueprint with id in Render. Stops automatic resource syncing via render.yaml but does not delete managed services or resources. Returns status 204 on success.
- **List all Render blueprint syncs** (List). List syncs for the blueprint with the provided id in Render. Returns sync objects including id, commit id, startedAt, completedAt, and state fields.
- **List all Render custom domains** (List). List custom domains for a service in Render using service_id. Returns fields id, name, domainType, publicSuffix, redirectForName, verificationStatus, createdAt, and server details.
- **Get single Render custom domain by ID** (Get). Get a custom domain for a service in Render using service_id and id. Returns id, name, domainType, publicSuffix, redirectForName, verificationStatus, createdAt, and server details.
- **Create a Render custom domain** (Create). Add a custom domain to the service with service_id in Render. Returns id, name, domainType, publicSuffix, redirectForName, verificationStatus, createdAt, and server details.
- **Delete a Render custom domain by ID** (Delete). Delete a custom domain for a service in Render using service_id and id. Returns 204 on success with no content.
- **List all Render services** (List). List services matching provided filters in Render. Returns service objects with fields including id, name, type, environmentId, ownerId, suspended status, createdAt, updatedAt, and serviceDetails such as buildCommand and url.
- **Get single Render service by ID** (Get). Retrieve service by id in Render. Returns id, name, type, ownerId, createdAt, updatedAt, dashboardUrl, autoDeploy, branch, buildFilter, environmentId, imagePath, notifyOnFail, registryCredential, rootDir, repo, slug, suspended, suspenders, and serviceDetails.
- **Create a Render service** (Create). Create a service in Render with required parameters type, name, and ownerId. Returns service id, name, type, ownerId, createdAt, updatedAt, dashboardUrl, and other service details.
- **Update a Render service by ID** (Update). Update service configuration by service id in Render. Returns updated service fields including id, autoDeploy, branch, buildFilter, createdAt, dashboardUrl, environmentId, imagePath, name, notifyOnFail, ownerId, registryCredential, repo, rootDir, slug, suspended, suspenders, type, updatedAt, serviceDetails, env, envSpecificDetails, lastSuccessfulRunAt, plan, region, runtime, schedule, and buildPlan.
- **Delete a Render service by ID** (Delete). Delete service by id in Render. Returns status 204 on success or error object with id and message on failure.
- **List all Render deploys** (List). List deploys for a service in Render using service_id. Returns deploy id, commit details (id, message, createdAt), image info (ref, sha, registryCredential), status, trigger, and timestamps (startedAt, finishedAt, createdAt, updatedAt).
- **Get single Render deploy by ID** (Get). Retrieve details of a specific deploy for a service in Render using service_id and id. Returns deploy id, commit info (id, message, createdAt), image info (ref, sha, registryCredential), status, trigger, and timestamps (startedAt, finishedAt, createdAt, updatedAt).
- **Create a Render deploy** (Create). Trigger a deploy for the service with id in Render. Returns deploy id, commit details (id, message, createdAt), image info (ref, sha, registryCredential), status, trigger, and timestamps (startedAt, finishedAt, createdAt, updatedAt).
- **Render deploys cancel** (Cancel). Cancel an in-progress deploy for a service in Render. Requires service_id and id. Returns deploy id, commit details (id, message, createdAt), image info (ref, sha, registryCredential), status, trigger, and timestamps (startedAt, finishedAt, createdAt, updatedAt). Not supported for cron jobs.
- **Render deploys roll back** (Action). Trigger a rollback to a previous deploy of the specified service in Render using service_id and deployId. Returns deploy id, commit details, status, trigger, and timestamps. Autodeploys remain enabled after rollback.
- **List all Render disks** (List). List persistent disks in Render filtered by ownerId, diskId, name, createdBefore, createdAfter, updatedBefore, updatedAfter, and serviceId. Returns disk id, name, sizeGB, mountPath, serviceId, createdAt, and updatedAt fields.
- **Get single Render disk by ID** (Get). Retrieve the persistent disk with the provided id in Render. Returns id, name, sizeGB, mountPath, serviceId, createdAt, and updatedAt fields.
- **Create a Render disk** (Create). Add disk with name, sizeGB, mountPath, and serviceId in Render. Returns id, name, sizeGB, mountPath, serviceId, createdAt, and updatedAt. Service must be redeployed for disk attachment.
- **Update a Render disk by ID** (Update). Update the persistent disk with id in Render. Requires the disk's associated service to be deployed and active. The response returns id, name, sizeGB, mountPath, serviceId, createdAt, and updatedAt fields.
- **Delete a Render disk by ID** (Delete). Delete a persistent disk by id in Render. All data on the disk will be lost and the associated service will lose access immediately. Returns status code 204 on success.
- **List all Render disk snapshots** (List). List snapshots for the persistent disk with the provided id in Render. Returns createdAt (snapshot creation time), snapshotKey (identifier), and instanceId (attached instance identifier).
- **Render disk snapshots restore** (Restore). Restore a persistent disk to an available snapshot in Render using diskId and snapshotKey. This irreversible operation overwrites current disk data and may trigger a service deploy. Returns id, name, sizeGB, mountPath, serviceId, createdAt, and updatedAt.
- **List all Render environment groups** (List). List environment groups in Render. Returns id, name, ownerId, createdAt, updatedAt, serviceLinks (id, name, type), and environmentId for each environment group.
- **Get single Render environment group by ID** (Get). Get environment group by id in Render. Returns id, name, ownerId, createdAt, updatedAt, serviceLinks (id, name, type), environmentId, envVars (key, value), and secretFiles (name, content).
- **Create a Render environment group** (Create). Create a new environment group in Render with required parameters name, ownerId, and envVars. Returns id, name, ownerId, createdAt, updatedAt, serviceLinks (id, name, type), environmentId, envVars (key, value), and secretFiles (name, content).
- **Update a Render environment group by ID** (Update). Update environment group name by id in Render. Returns id, name, ownerId, createdAt, updatedAt, serviceLinks (id, name, type), environmentId, envVars (key, value), and secretFiles (name, content).
- **Delete a Render environment group by ID** (Delete). Delete environment group by id in Render, including all environment variables and secret files it contains. Returns status 204 on success.
- **Get single Render environment variable by ID** (Get). Retrieve a particular environment variable in a specific environment group in Render. Requires env_group_id and env_var_key. Returns key and value of the environment variable.
- **Update a Render environment variable by ID** (Update). Add or update an environment variable in a specific environment group in Render. Requires env_group_id and env_var_key. Returns id, name, ownerId, createdAt, updatedAt, serviceLinks (id, name, type), environmentId, envVars (key, value), and secretFiles (name, content).
- **Delete a Render environment variable by ID** (Delete). Remove a particular environment variable from a specific environment group in Render. Requires env_group_id and env_var_key. Returns 204 on success.
- **Get single Render secret file by ID** (Get). Retrieve a particular secret file by envGroupId and secretFileName in Render. Returns name and content of the secret file.
- **Update a Render secret file by ID** (Update). Add or update a secret file in Render by envGroupId and secretFileName. Returns id, name, ownerId, createdAt, updatedAt, serviceLinks (id, name, type), environmentId, envVars (key, value), and secretFiles (name, content).
- **Delete a Render secret file by ID** (Delete). Remove a secret file from an environment group in Render. Requires envGroupId and id. Returns 204 on success with no content.
- **List all Render logs** (List). List logs for ownerId with filters resource, startTime, and endTime in Render. Returns hasMore, nextStartTime, nextEndTime for pagination and logs with id, message, timestamp, and labels.
- **List all Render subscribe logs** (List). Subscribe to new logs for ownerId filtered by resource. Returns real-time log entries with id, message, timestamp, and labels including resource, instance, host, statusCode, method, level, type, text, and path.
- ...and 94 more tools. Call `tools/list` via the MCP endpoint, or see the full catalog via the API, for the complete set.
