Claude Retool connectorWhat Claude can do in your Retool account.
The Claude Retool connector exposes 23 tools. 16 read your organization (apps, resources, workflows, users), 6 change something in it, and 1 is described nowhere. Here is what Claude can reach, depending on the scopes you grant.
Verified Trustpilot reviews · AI, automation & growth agency
What the Claude Retool connector changes for your team
An access review, an inventory of internal apps or the question "which databases are connected?" no longer means jumping between screens in Retool. You ask Claude, it queries your organization and answers. What it can reach, though, depends on scopes, the access levels you pick when you authorize it.
Run the access review. retool_list_users and retool_list_user_invites bring back users and pending invitations; retool_delete_user_invite cancels the ones that no longer make sense.
Map your internal tooling. retool_list_apps, retool_list_resources and retool_list_workflows give you the inventory of apps, data sources and workflows in one pass.
Answer a numbers question. After retool_get_resource_typescript_definitions, retool_execute_resource_typescript runs code against your resources for an analysis.
What Claude cannot do here: without the admin scope, most of the tools on the sheet stay closed to it. It only sees objects your account can see. And the sheet exposes only part of what Retool documents for its server. Nothing runs on its own either: no tool reacts to an event unless you ask. For that, you need an automation platform, a different job; the Integrations hub covers that side.
The vocabulary in one minute
Five words worth knowing before you connect Retool.
- Connector
- The link you set up once between Claude and your Retool organization, so Claude can work in it while answering you.
- Tool
- One named action the connector opens to Claude. It decides which to call; the directory sheet lists them by name.
- Authorization
- Retool's sign-in screen, where you grant Claude its access scope by scope. Given once per person, and revocable later.
- Approval
- The confirmation Claude waits for before carrying out something that changes your account, shown right in the chat.
- MCP
- The open standard connectors are built on; it is what lets an assistant talk to an outside service.
Connect Retool to Claude in three steps
- 01
Find Retool in Claude
In Claude's settings, open Customize then Connectors and look for Retool. On a Team or Enterprise plan, an Owner or Primary Owner has to enable it for the organization first.
- 02
Start the connection
Click Connect on Retool's row, then sign in through the window Retool opens itself. If the link breaks later, use Disconnect and reconnect from the same row.
- 03
Pick and confirm the access
The authorization screen belongs to Retool, and Retool, not Claude, decides what the access covers. Read it before you confirm. You can withdraw the access later from your Retool account.
All 23 tools, grouped by effect
Retool gives Claude 23 tools: 16 that read your account, 6 that change something in it, and 1 no official source describes.
Three groups: what Claude reads, what it changes, and what no source describes. Tool names stay exactly as Claude shows them.
- 16 read
- 6 write
- 1 not documented
What Claude reads (16)
16 toolsSixteen tools that look at your Retool organization, many of them behind the admin scope.
retool_list_resources
Lists the resources available in your Retool organization, including databases, APIs, storage and AI providers. Retool counts listing every connected resource and its configuration among the server's uses.
retool_get_resource
Pulls the metadata of one resource by name. Retool is explicit: this is a description of the resource, not a query against the data it holds.
retool_get_resource_typescript_definitions
Generates the global variable bindings and TypeScript definitions for selected resources, the step Retool requires before any code can run against them. Retool's reference lists it under a shorter name, with ts in place of typescript.
retool_list_workflows
Lists the workflows in your Retool organization. Like the other organization-level tools, it belongs to the admin set in Retool's reference.
retool_get_organization
Returns your Retool organization's settings. Retool cites inspecting organization configurations among the things its server is meant for.
retool_get_workflow
Opens one workflow by its ID so Claude can tell you what Retool returns about it. Nothing in the workflow is altered.
retool_list_folders
Returns the folders in your Retool organization as a list. It is one of the read tools Retool places behind the admin scope.
retool_get_environment
Describes one environment from its ID. Retool lists inspecting organization and resource environment configurations among the server's uses.
retool_list_environments
Shows every environment defined in the organization. A single one can then be opened in detail with retool_get_environment.
retool_get_folder
Returns one folder by its ID, as Retool exposes it to an account with administrator access.
retool_list_user_invites
Lists the user invites in your organization. Retool names managing pending invites among the server's uses.
retool_get_app
Fetches one Retool app by its ID and returns what Retool exposes about it.
retool_list_apps
Lists the apps in your Retool organization. It is one of the few tools on the sheet that only needs the mcp:read scope.
retool_get_user
Shows one user of the organization from their ID. Retool names auditing the users who have access to the organization among the server's uses.
retool_get_user_invite
Opens one user invite from its invite ID and returns what Retool records about it. Nothing is sent or cancelled.
retool_list_users
Lists the users in your Retool organization. Retool names auditing who has access to the organization among the intended uses.
What Claude changes (6)
6 toolsSix tools that run code, delete, or manage invitations. No source gives them their own confirmation.
retool_execute_resource_typescript
Approval: see the ruleExecutes a TypeScript snippet against selected resources, using the bindings generated just before. Retool lists writing queries against resources for data analysis among the server's uses.
retool_delete_workflow
Approval: see the ruleDeletes a workflow from the organization by its ID.
retool_create_user_invite
Approval: see the ruleCreates a user invite for your Retool organization. Retool lists bulk-inviting users among the server's uses.
retool_delete_user_invite
Approval: see the ruleDeletes a pending invitation from its ID.
retool_delete_user_invite_attribute
Approval: see the ruleDeletes a user attribute from a pending user invite.
retool_set_user_invite_attribute
Approval: see the ruleCreates or updates a user attribute on a pending user invite.
Undocumented (1)
1 toolThe directory publishes this name and nothing else. No official text says what it does, and we will not guess from the name.
retool_generate_react_app
This name appears on the directory sheet, and nothing more. Retool's tool reference does not describe it, and no Anthropic page does either, so this page will not say more.
What Claude asks before it acts
By default, Claude stops and asks for your go-ahead before each action it takes on an account for you, inside the conversation.
On Team and Enterprise, owners decide whether members can let some actions through without being asked every time, and they can cap what a connector does for the whole organization. On the Retool side there is a second barrier: scopes. Retool says you cannot be granted a scope wider than your own account allows, and that you only see objects you have permission to view. An app hidden from you in Retool stays hidden from Claude too.
Which plans include the connector
None of the 819 sheets in the official directory shows availability by plan; connector by connector, the information is not published anywhere.
Anthropic's general rule is documented: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile, and on Team and Enterprise an Owner or Primary Owner enables the connector before members connect. Retool's documentation describes a different path depending on the plan, which the limits section sets side by side. For the current state, check Retool's sheet in the directory.
Where the Retool connector stops
A connector is not an automation: Claude calls these tools while it answers you, and nothing starts by itself.
The directory sheet exposes 23 tools, while Retool's reference documents many more for its server (app access, groups, audit logs, app building, publishing). It does not, however, describe the retool_generate_react_app tool on the sheet. The sheet is what tells you what Claude actually has. This connector is documented by Retool alone, and the directory badge is not a security audit: Anthropic does not vouch for how a publisher's tools behave.
How do you connect Retool depending on your Claude plan?
- Claude Help Center, general connector rule ↗September 2026Remote connectors are open to all users; on Team and Enterprise, an Owner first enables the connector for the organization.
- Retool documentation ↗read on 1 October 2026The publisher says that on Team or Enterprise an Owner adds Retool's server as a custom connector, and that on Free, Pro or Max you go through Browse connectors.
What this page followsThe two texts do not disagree on availability so much as on the route. Anthropic describes enabling the directory connector, Retool describes its own path. Neither is out of date, and it is the publisher speaking for itself: check the directory sheet from your own account before picking a route.
Need help connecting Retool to Claude?
A person reads every message.