Retool MCP Server

Manage Retool apps, workflows, resources, users, and invites from AI coding agents via Retool's official OAuth2-authenticated MCP server.

Developer Tools by Retool OAuth2 active

Connect (Remote Server) Docs

Overview

Retool's MCP server is an official, provider-hosted endpoint that lets AI coding agents like Claude, Cursor, Codex, ChatGPT, and Kiro interact with a Retool organization directly. Instead of jumping into the Retool web UI, builders and administrators can list apps, inspect resources, audit users, manage invites, and execute TypeScript against connected data sources from inside their AI assistant.

The server is hosted per-organization at https://<your-retool-instance>/mcp and uses OAuth 2.0, so all actions inherit the existing role and permission model in Retool. Tools are split into two scopes: mcp:read for read-only operations against apps and resources, and mcp:admin for administrative actions like managing users, invites, workflows, folders, and environments. The server also exposes a TypeScript execution tool, allowing agents to query connected resources programmatically.

The product is currently in public beta (announced May 8, 2026). Retool has indicated that future versions will add the ability to build and edit Retool apps from natural language descriptions, deploying directly to the platform.

Tools

Tool	Description
`retool_list_apps`	Lists apps in the Retool organization.
`retool_get_app`	Retrieves details for a specific Retool app.
`retool_list_resources`	Lists connected data source resources.
`retool_get_resource`	Fetches configuration for an individual resource.
`retool_get_resource_typescript_definitions`	Returns TypeScript type definitions for a resource, used to author queries.
`retool_execute_resource_typescript`	Executes TypeScript code against a connected resource to run queries or analysis.
`retool_list_audit_logs`	Reads organization audit trail events.
`retool_list_workflows`	Lists Retool Workflows.
`retool_get_workflow`	Retrieves a specific workflow definition.
`retool_delete_workflow`	Deletes a workflow.
`retool_list_folders`	Lists app and resource folders.
`retool_get_folder`	Retrieves a specific folder.
`retool_list_environments`	Lists Retool resource environments (e.g. staging, production).
`retool_get_environment`	Retrieves a specific environment configuration.
`retool_list_users`	Lists users in the organization.
`retool_get_user`	Retrieves details for a specific user.
`retool_get_organization`	Returns organization-level details.
`retool_list_user_invites`	Lists pending user invites.
`retool_get_user_invite`	Retrieves a specific user invite.
`retool_create_user_invite`	Creates a new user invite, optionally in bulk.
`retool_delete_user_invite`	Revokes a pending user invite.
`retool_set_user_invite_attribute`	Sets a custom attribute on a user invite.
`retool_delete_user_invite_attribute`	Removes a custom attribute from a user invite.

Setup Guide

Prerequisites

A Retool organization (Cloud or self-hosted) where you are an admin or have appropriate permissions
The MCP feature enabled (currently in public beta)
An MCP-compatible client (Claude Desktop, Claude Code, Cursor, Codex, ChatGPT with Developer mode, Kiro, or a Retool Agent)

The server URL follows the pattern https://<your-retool-instance>/mcp, for example https://example.retool.com/mcp. Authentication is OAuth 2.0, so the first connection triggers a browser-based login flow.

Claude Code / Claude Desktop

Run from terminal:

claude mcp add --transport http retool https://<your-retool-instance>/mcp

Restart Claude, then authenticate when prompted in the browser.

Cursor

Add to .cursor/mcp.json:

{
  "mcpServers": {
    "retool": {
      "type": "http",
      "url": "https://<your-retool-instance>/mcp"
    }
  }
}

Restart Cursor to trigger the OAuth flow.

ChatGPT

Enable Developer mode, then go to Settings > Apps > Advanced settings, create an app pointing at https://<your-retool-instance>/mcp with OAuth authentication selected.

Retool Agents

In Retool, create an MCP Server resource under the Resources tab, set the server URL, click "Auto-configure authentication" and "Connect with OAuth," then add the tool to your agent.

Codex and Kiro

Both support command-line configuration with automatic OAuth prompts on first use; point them at the same https://<your-retool-instance>/mcp URL.

Use Cases

Audit user access across a Retool organization and list pending invites from a chat agent before a compliance review
Bulk-invite new hires to Retool from a CSV or HR system, assigning groups and attributes in one prompt
Query connected production databases via retool_execute_resource_typescript to answer ad-hoc data questions without opening Retool
List and inspect existing apps, workflows, and resources to document an organization's internal tooling footprint
Pull audit logs into an AI agent to investigate a specific user action or resource configuration change

Example Prompts

"List all Retool resources in our org and tell me which ones point at production databases."
"Invite alice@example.com and bob@example.com to Retool, add them to the Engineering group, and confirm the invites were created."
"Show me audit log entries for user charlie@example.com in the last 7 days."
"Run a TypeScript query against the analytics_postgres resource to count signups grouped by day for the last 30 days."
"List all workflows in our Retool org and flag any that have not been edited in over a year."

Pros

Official, Retool-hosted server with OAuth 2.0, so it inherits existing org permissions and governance
Broad coverage of administrative surface area: apps, resources, workflows, users, invites, audit logs, environments
Includes a TypeScript execution tool that lets agents actually query connected resources, not just read metadata
First-class setup instructions for Claude, Cursor, ChatGPT, Codex, Kiro, and Retool Agents

Limitations

Public beta as of May 2026, so tool surface and behavior may still change
No tools yet for building or editing Retool apps from natural language; that capability is on the roadmap but not shipped
Admin-scoped tools require the mcp:admin scope, so non-admin builders have a narrower set of capabilities

Alternatives

Retool's REST API (https://docs.retool.com/reference/api) wrapped in a custom MCP server for users who need capabilities beyond the official tool set
Community-built TechnicalRhino/retool-mcp GitHub project, an unofficial self-hosted MCP server targeting Retool (not maintained by Retool)
Direct Retool Agents inside Retool itself, which can call internal tools without an external AI client