# Retool MCP connector

The Retool connector brings Retool users, groups, spaces and folders into Claude, ChatGPT, Cursor, Microsoft Copilot and any MCP client through one governed endpoint, where every call runs as the signed-in person and lands in the audit log.

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

## Facts

| | |
| --- | --- |
| Application | Retool |
| Category | Application Development |
| AI tools | 160 |
| 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 Retool is connected

- Which Retool groups is Priya Shah in?
- Create a Retool space for the APAC support team.
- List everyone in the Finance Admins group.

## Connect Retool in Elaichi

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

1. Open Connections, choose Add connection, and pick Retool.
2. Optionally set Share with, then press Connect.
3. Paste a Retool API key. One person generates a token in Retool 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 Retool tools are exposed, rename them, or freeze arguments before anyone points a client at it.

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

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

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

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

## Retool 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 Retool 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 Retool 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 Retool through Elaichi

### Onboard a new hire into Retool

IT. Create the Retool account, add the person to the right groups and place them in the right space before their first login, all from one ask.

### Review who can reach each space

Security. Pull the list of Retool users and groups for a space and check it against who should actually be there, without clicking through every group page.

### Tidy folders before a release

Engineering. Create the folders a new set of apps needs, rename the ones that drifted and remove the empty ones, so the team can find things when the release goes out.

### Keep groups matched to the org chart

Operations. When someone changes teams, remove them from the old Retool groups and add them to the new ones in one pass, with the change recorded in the audit log.

### Set up a space for a new region

Platform. Create a Retool space for a new region or business unit, create its groups and add the first members, ready for the people building there.

### Offboard a leaver the same day

People Ops. On someone's last day, remove them from every Retool group and delete the user, so there is no account left behind to clean up later.

## Elaichi vs Zapier MCP vs Composio for Retool

All three can connect Retool 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 Retool tools | Allow or restrict single Retool 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 Retool 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 Retool to Claude?

Connecting Retool to Claude takes two steps. First, connect Retool in Elaichi by pasting a Retool API key; there is no OAuth application to register and no client ID or secret to generate. Then open Claude, go to Customize, then Connectors, then Add, and paste the Elaichi endpoint, https://api.elaichi.ai/mcp. Claude signs you in over OAuth and your Retool users, groups and spaces are ready to ask about.

### Does Retool work with ChatGPT and Cursor as well as Claude?

Yes. Once Retool is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client and the Elaichi Agent. You connect Retool once and every client you use picks it up.

### What can an AI agent actually do with my Retool data?

An agent can list the users in your Retool organization, tell you which groups someone belongs to, create a new user, add or remove group members, and set up spaces and folders. It can also update names and details on Retool users, groups, spaces and folders when they change. Short, concrete asks such as remove Dana from the Finance Admins group work better than long sentences.

### Does connecting Retool give the AI access to every user, group and space?

No. A Retool connection in Elaichi runs with the access of the person who signed in and the permissions behind the key that was connected, so an agent can only see and change what that access already allows in Retool. Elaichi can narrow that further with roles and restrictions, and it never widens it.

### Can my team share one Retool connection?

Yes. One admin connects Retool in Elaichi and shares the connection with a team, and nobody else ever handles the Retool API key. Each teammate still signs in to Elaichi as themselves, so the audit log names the person behind every change to a Retool user, group or space.

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

Yes. Restrictions in Elaichi work per action, so you can restrict deleting Retool users, groups, spaces or folders on a role or on one person while leaving reading and creating open. A restricted tool still appears in Elaichi's tool search, flagged as restricted, but no client can run it, whatever the prompt says.

### What happens to a Retool connection when someone leaves?

Offboarding someone in Elaichi ends their access to the Retool connection at once, across every client. A shared Retool connection keeps working for everyone else who uses it. If you ever want to remove Retool entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client.

### Does the Retool MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. Retool 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 Retool?

Yes. Both let Claude, ChatGPT or Cursor use Retool. 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 Retool call.

### How is Elaichi different from Composio for Retool?

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 Retool: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

## All 160 Retool tools

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

- **List all Retool users** (List). List Retool users in the organization. Returns: id, email, active, first_name, last_name, is_admin, user_type, created_at. Filter by email, first_name, or last_name.
- **Get single Retool user by ID** (Get). Get a single Retool user by id. Returns: id, email, active, first_name, last_name, is_admin, user_type. Required: id, userId.
- **Create a Retool user** (Create). Create a user in Retool. Returns the created user including id, email, first_name, last_name, active, created_at, user_type, seat_type, and metadata. Required: email, first_name, last_name. seat_type requires the Named Seats feature on your plan.
- **Delete a Retool user by ID** (Delete). Delete a user in Retool by id. Disables the user from the organization rather than permanently removing the account. Returns an empty 204 response on success. Required: id.
- **Update a Retool user by ID** (Update). Update a Retool user by id using JSON Patch operations (op: add, remove, or replace). Returns the updated user including id, email, first_name, last_name, active, created_at, user_type, and seat_type. Required: id, operations.
- **List all Retool groups** (List). List Retool permission groups for the organization or a space. Returns: id, legacy_id, name, members, universal_app_access, universal_resource_access, universal_workflow_access, created_at, updated_at.
- **Get single Retool group by ID** (Get). Get a single Retool permission group by its numeric id. Returns: id, legacy_id, name, members, universal_app_access, universal_resource_access, created_at, updated_at. Required: id, groupId.
- **Create a Retool group** (Create). Create a Retool permission group. Returns the created group: id, name, members, universal access levels, created_at. Required: name. Members, user invites, and access levels can be set at creation.
- **Delete a Retool group by ID** (Delete). Delete a Retool permission group by id, revoking its access to apps, resources, and workflows. Returns an empty 204 response on success. Required: id.
- **Retool groups partial update** (Update). Update a Retool group partially using a list of patch operations. Returns the updated group: id, name, members, universal access levels, updated_at. Required: group_id, operations.
- **Update a Retool group by ID** (Update). Replace a Retool group entirely with the supplied fields. Returns the updated group: id, name, members, universal access levels, updated_at. Required: id.
- **List all Retool spaces** (List). List Retool spaces. Returns the child spaces within the current space, each with: id, name, domain, created_at, and updated_at.
- **Get single Retool space by ID** (Get). Get a single Retool space by id. Returns: id, name, domain, created_at, updated_at. Required: id.
- **Create a Retool space** (Create). Create a Retool space for isolated, multitenant experiences. Returns the created space with id, name, domain, created_at, and updated_at. Required: name, domain. On Retool Cloud, domain is the space's subdomain.
- **Delete a Retool space by ID** (Delete). Delete a Retool space by id. Returns an empty 204 response on success. Required: id.
- **Update a Retool space by ID** (Update). Update a Retool space by id. Returns the updated space with id, name, domain, created_at, and updated_at. Required: id, name, domain.
- **List all Retool organizations** (List). List Retool organizations with their usage data, covering page views, active users, and app activity across organizations. Returns: org_id, host, last_active.
- **Retool organizations bulk update** (Update). Update Retool organization settings by applying a batch of patch operations. Returns: id, request_access_enabled, release_management_enabled, preloaded_css, two_factor_auth_required. Required: operations.
- **Create a Retool folder** (Create). Create a Retool folder for apps, workflows, resources, agents, or libraries. Returns: success, data. Required: name, folder_type.
- **Delete a Retool folder by ID** (Delete). Delete a Retool folder (app, workflow, resource, agent, or library) by id. Returns an empty 204 response on success. Required: id, folderId.
- **Get single Retool folder by ID** (Get). Get a single Retool folder by id. Returns: success, data. Required: id.
- **List all Retool folders** (List). List Retool folders for apps, workflows, resources, agents, and libraries in your organization. Returns: success, data.
- **Update a Retool folder by ID** (Update). Update a Retool folder by id using RFC 6902 JSON Patch operations. Returns: success, data. Required: id, operations.
- **Delete a Retool group member by ID** (Delete). Remove a user from a Retool group. Returns the updated group including id, name, members, universal_app_access, and created_at. Required: id, group_id, groupId, userId.
- **Create a Retool group member** (Create). Add users to a Retool group and optionally set or unset group admin status. Returns the updated group: id, name, members, universal access levels, created_at. Existing members cannot be removed with this endpoint. Required: group_id, groupId, members.
- **Create a Retool group user invite** (Create). Add user invites to a Retool group. Returns the updated group including id, name, members, user_invites, and universal access levels. Required: group_id, groupId, userInviteIds.
- **Delete a Retool group user invite by ID** (Delete). Remove a pending user invite from a Retool permission group. Returns an empty 204 response on success. Required: id, group_id, group_id, userInviteId.
- **Create a Retool spaces copy element** (Create). Copy apps, queries, resources, and workflows to another Retool space. Returns: resource_ids, query_library_query_ids, app_ids, workflow_ids. Required: destination_space_id. Dependent elements are copied automatically; omit id lists for element types you are not copying.
- **Create a Retool user logout** (Create). Log out a Retool user by id, terminating all their active sessions and optionally initiating an RP-initiated SSO logout. Returns: sso_logout, sso_logout_url, warning. Required: user_id, userId.
- **Retool user user attributes bulk delete** (Delete). Delete a user attribute from a Retool user. Returns: metadata (the user's updated user metadata). Required: user_id, attribute_name.
- **Create a Retool user user attribute** (Create). Create or update a user attribute on a Retool user. Returns: metadata (the updated user metadata containing the new attribute value). Required: user_id, user_id, name, value.
- **Update a Retool users reset 2 fa by ID** (Update). Reset a user's two-factor authentication in Retool, disabling all two-factor authentication methods for the specified user. Returns an empty 204 response on success. user_1234). Required: id.
- **Create a Retool app delete** (Create). Delete an app's entry from a named Retool release manifest by pushing a delete branch to source control. Returns: commit_sha, url, branch_name. Deprecated — use the element-based delete endpoint instead. Required: app_uuid, manifest_name.
- **List all Retool app themes** (List). List all app themes for your Retool organization or space. Returns themes with id, legacy_id, name, theme, created_at, and updated_at.
- **Retool app themes bulk update** (Update). Create or update an app theme in Retool by sending its full record. Returns: success, data. Required: id, legacy_id, name, theme, created_at, updated_at. Fails with 409 if a theme with the same name already exists.
- **Create a Retool app theme** (Create). Create a new app theme in Retool. Returns: id, legacy_id, name, theme, created_at, updated_at. Required: id, legacy_id, name, theme, created_at, updated_at. Fails with 409 if a theme with the same name already exists.
- **Delete a Retool app theme by ID** (Delete). Delete an app theme in Retool by id. Returns an empty 204 response on success. Required: id. Available for classic apps only.
- **Get single Retool app theme by ID** (Get). Get a single Retool app theme by id. Returns the theme with id, legacy_id, name, theme, created_at, and updated_at. Required: id.
- **Create a Retool branches reset** (Create). Reset a Retool app branch by discarding Retool-local branch changes and reloading app contents from a remote Git branch. Returns: branch_name, remote_branch_name, status, updated_apps. Required: branch_name. Updates to non-page elements on the branch are not persisted.
- **Create a Retool delete** (Create). Delete an element from a Retool release manifest by pushing a source control branch that removes its entry. Returns: commit_sha, url, branch_name. Requires multi-instance releases to be enabled. Required: element_type, element_uuid, manifest_name.
- **Update a Retool manifest app by ID** (Update). Set the release version for an app in a Retool release manifest by pushing a branch to source control; the manifest is created in the branch if it does not exist. Returns: commit_sha, url, branch_name. This endpoint is deprecated. Required: id, manifest_name, release.
- **Create a Retool manifest delete** (Create). Delete a named release manifest in Retool by pushing a branch to the source control repository that removes it. Returns: commit_sha, url, branch_name. Required: manifest_name, manifestName.
- **Create a Retool releases app** (Create). Create a release artifact for a Retool classic app by pushing a source control branch with the given version. Returns: commit_sha, url, branch_name. Deprecated: supports classic apps only; use the newer releases endpoint instead. Required: app_id, appUuid, release_version.
- **Get single Retool releases app by ID** (Get). List all available releases for a Retool classic app. Returns: release_version, release_description, created_at. Required: id. Deprecated: supports classic apps only; use the newer releases endpoint instead.
- **Create a Retool source control branch** (Create). Create a Retool source control branch, optionally initialized with a single element. Returns: branch_id, branch_name, shared, and element. Required: branch_name. When element_id is provided, element_type is also required (PAGE, PLAYGROUND_QUERY, WORKFLOW, PROCESS, or AGENT).
- **Retool source control configs bulk delete** (Delete). Delete the Retool source control configuration for the organization or space, removing the Git provider connection. Returns an empty 204 response on success.
- **Retool source control configs bulk update** (Update). Set the Retool source control configuration for the organization or space, overwriting any existing configuration. Returns: config, provider, org, repo, default_branch, repo_version. Required: config.
- **Create a Retool source control config** (Create). Create the Retool source control configuration for the organization or space. Returns: config, provider, org, repo, default_branch, repo_version. Required: config. Fails if a configuration is already set.
- **List all Retool source control configs** (List). Get the Retool source control configuration for the organization or space. Returns: config, provider, org, repo, default_branch, repo_version.
- **Get single Retool source control deployment by ID** (Get). Get a Retool source control deployment by id. Returns: id, status, commit_sha, triggered_by, created_at, completed_at, app_deployment_details. Required: id.
- ...and 110 more tools. Call `tools/list` via the MCP endpoint, or see the full catalog via the API, for the complete set.
