Claude + Retool: What the Integration Can (and Can't) Do in 2026
Retool ships its own official MCP server, so Claude really can build apps, run queries, and manage users inside your Retool org — no third-party glue required. Retool announced the server on May 8, 2026, it’s in public beta, and it works for both cloud and self-hosted customers. If you’d rather stay lower-level, Retool also exposes a REST API with bearer-token auth, and there’s a small community MCP server for self-hosted setups.
Here’s each route, when to pick it, and what to use when you want Retool work that happens without you at the keyboard.
Route 1: Retool’s official MCP server
This is the one to reach for first. Retool’s official MCP server lets Claude — plus Cursor, Codex, ChatGPT, and Kiro — manage your Retool org directly from your AI environment.
- Endpoint:
https://<your-retool-instance>/mcp - Transport: remote HTTP (not a local stdio process)
- Auth: OAuth 2.0 — you authorize once, and the server inherits the same permissions your Retool account already has
- Availability: public beta, cloud and self-hosted
What Claude can actually do through it: build and edit apps, execute queries against your connected data sources, bulk-invite and audit users, inspect environment configuration, and list connected resources. Because auth is OAuth against your own account, changes stay inside the security model your org already approved.
To connect it in Claude Desktop, add the remote MCP server under Settings → Connectors (or via the config file for an HTTP server), point it at your instance’s /mcp URL, complete the OAuth handshake in the browser, and restart Claude. Retool’s docs carry per-client setup steps.
Route 2: The Retool REST API + an access token
If you want Claude to hit Retool programmatically — inside Claude Code, a script, or your own MCP wrapper — use the REST API directly.
- Base URL:
https://<your-retool-instance>/api/v1 - Auth: a bearer token you generate under Settings → API → Access Tokens (shown once at creation — copy it immediately)
- Scopes: granular, e.g.
users:read,users:write,groups:read,groups:write
The public API is strongest for org administration — full user CRUD and group-membership management — rather than reading app internals. In Claude Code you can hand Claude the token as an environment variable and let it call the endpoints with curl or fetch; for a persistent tool, wrap those calls in a thin HTTP-MCP server. This route is the honest fallback when the MCP beta doesn’t cover a specific admin action you need to script.
Route 3: The community self-hosted MCP server
There’s also a small community project — TechnicalRhino/retool-mcp (~2 stars, JavaScript, run via npx) — aimed at self-hosted Retool instances. It exposes tools for listing/creating/deleting apps and releases, managing folders, triggering workflows, viewing resources, user and group management, and pulling audit logs, all against your instance’s API.
It’s genuinely niche and predates or overlaps the official server, so for most people the official MCP server is the better, better-supported choice. Reach for the community repo only if you’re self-hosted and want an API-token-based tool you can read and modify yourself.
Route 4: Retool’s own agents (worth knowing)
Retool isn’t just a target here — it has its own AI product. Retool Agents act as MCP clients: they can connect out to remote MCP servers (GitHub, Slack, Stripe, Cloudflare, Docker, and more) over HTTP, with OAuth / Basic / Bearer auth and a 2-minute tool timeout. So Claude can drive Retool, and Retool’s own agents can drive other tools. Different jobs, but useful to know the platform sits on both sides of MCP.
The limits that actually matter
- The official server is beta. Expect the tool set to shift, and don’t wire it into anything load-bearing without testing.
- No triggers. MCP tools only run inside a Claude session you start. Nothing fires “when a workflow fails” or “every morning at 9” on its own.
- Laptop-bound. Claude Desktop’s connection lives on your machine. Close the laptop and the automation stops.
- claude.ai on the web can reach the official remote MCP server (it’s HTTP + OAuth), but it cannot see a local stdio server, the community
npxserver, or a self-hosted instance that isn’t publicly reachable. - The public API is admin-shaped, so token-based scripting is great for users/groups and thinner for deep app data.
Claude + Retool’s MCP server is excellent for building, editing, and administering Retool on demand while you work. It’s not built for Retool work that has to run on a schedule or a trigger while you’re away.
If you want Retool work that runs on its own: Carly
Carly reaches Retool through your own Retool API key (paste it on the integrations page) — one of 200+ native integrations plus anything with an API. The difference from Claude is that Carly runs on triggers and schedules, not inside a chat window.
- When a Retool workflow fails, Carly can pull the audit log, summarize the cause, and post it to your team channel.
- Every morning, Carly can hit your Retool admin API, diff the user list, and email you who was added or deactivated overnight.
- When a new hire lands in your HRIS, Carly can bulk-invite them to the right Retool groups without you opening the console.
- No-code setup: you don’t write config. Carly interviews you about what should happen, then builds the workflow.
- Actually sends — Carly drafts and sends through Gmail and Outlook, so the output lands in a real inbox.
- Connects to anything — 200+ native integrations, plus any tool with an API via your own key, so a Retool step can sit next to Slack, a database, and your CRM in one flow.
AI agents start at $35/month, and steps in a workflow that don’t use AI run free and unlimited.
Claude vs Carly
| Capability | Claude + Retool MCP | Carly |
|---|---|---|
| Read/search Retool apps & users | Yes (official MCP server) | Yes (via API key) |
| Build/edit apps in a session | Yes | Not its focus |
| Acts on triggers | No | Yes |
| Runs on a schedule | No | Yes |
| Works while laptop is closed | No | Yes |
| Sends email (Gmail/Outlook) | No | Yes |
| Connects other tools in one flow | One at a time | 200+ native + BYO-key |
| Pricing | Pro $20 / Max $100–$200 | AI agents from $35/mo |
Claude is the best way to build and administer Retool hands-on from your AI environment; Carly is the way to make Retool part of workflows that run without you.
Frequently Asked Questions
Does Claude work with Retool?
Yes. Retool ships an official MCP server (https://<your-instance>/mcp, OAuth) that Claude can connect to, letting it build apps, run queries, and manage users. You can also drive Retool’s REST API directly from Claude Code.
Is there an official Retool MCP server in 2026?
Yes — Retool announced it on May 8, 2026, and it’s in public beta for both cloud and self-hosted customers. It uses HTTP transport and OAuth 2.0, so no API token is required for the MCP route.
Can claude.ai on the web access Retool?
For the official remote MCP server, yes — it’s HTTP + OAuth, so the web app can authorize it. The web app cannot reach a local/community npx server or a self-hosted instance that isn’t publicly accessible.
Can Claude manage Retool users or workflows automatically?
Only when you’re in a session. Claude can invite users or trigger workflows on request, but it won’t run anything on a schedule or in response to an event on its own — that’s what a trigger-based tool like Carly is for.
More: Carly integrations · Claude connectors, explained · Claude + GitHub · Claude + Slack · Claude vs Carly
Ready to automate your busywork?
Carly schedules, researches, and briefs you—so you can focus on what matters.
See what people say
"Before Carly, I relied on a Calendly link, but the whole process felt impersonal and not very professional. Carly changed that by handling all the back-and-forth, so I'm no longer stuck in endless email threads trying to line up schedules.
Now Carly reaches out to candidates, shares my real-time availability, lets them pick a slot, then sends a Zoom link and drops it straight into my calendar. She sends reminders to both of us before each call, which has significantly reduced no-shows and last-minute confusion.
On top of scheduling, Carly acts like a full executive assistant, sending me my schedule the night before so I can prepare for each call. It reminds me of the old x.ai assistant, but Carly is noticeably smarter, faster, and better suited to my healthcare recruitment business."
