Retool MCP

Retool organizations accumulate the kind of administrative state nobody enjoys clicking through — who has access to which app, which resources point at production, which invites are still pending. Retool's official MCP server exposes that surface to an agent over a per-instance HTTP endpoint.

Connecting

The endpoint lives on your own Retool instance, not a shared vendor host: https://<your-instance>.retool.com/mcp, over HTTP with OAuth 2.0. The authorization flow triggers automatically on the first tool call, and you choose which scopes to grant at that point — so the agent's reach is decided per connection rather than baked into a long-lived token.

claude mcp add --transport http retool https://example.retool.com/mcp
codex mcp add retool --url https://example.retool.com/mcp
kiro-cli mcp add --name "Retool" --scope global --url "https://example.retool.com/mcp"

Cursor users can add it to .cursor/mcp.json as {"type": "http", "url": "https://example.retool.com/mcp"}.

What it covers today

Current tooling centres on organization and user administration:

• Querying Retool resources for data analysis
• Bulk user invitations and pending-invite management
• Auditing user access across the organization
• Inspecting organization settings and resource environment configuration
• Listing connected resources and reviewing their configuration

Status

The server is in public beta (documented April 2026), live on Retool Cloud across all plans. Retool states it is actively adding tools to widen coverage toward more of the platform — app building included — so the tool list is expected to grow. Run tools/list after connecting to see exactly what your instance and granted scopes expose, rather than relying on a published list that may lag.

Best suited to teams already running Retool at organizational scale, where access auditing and user administration are recurring chores worth handing to an assistant.