01 · Records and state owned
Organizations, users and invites, apps and build activity, function runs, audit logs, connected resources, and resource environment configurations.
Retool
Retool
A leading platform for building internal and embedded applications directly over production databases and APIs, making it an explicit implementation layer for BYO-UI.
Interface hosts, builders & integration infrastructureInterface host and orchestration layerExtensible SaaS
Concrete capability record
Data, retrieval, actions, identity, and operating limits
A field-by-field summary of what the reviewed first-party references actually support. Publisher update dates and BYO-UI review dates are shown separately below.
02 · Data you can retrieve
Inspect apps, current and past agent activity, function runs, users and access, audit logs, connected resources, and organization or resource environment configuration.
03 · Actions and write paths
Import React apps, start or continue app builds, cancel failed builds, manually review function runs, write resource-backed analysis queries, bulk-invite users, and manage pending invites.
04 · Authentication and permissions
OAuth 2.0 authorization presents selectable scopes. MCP actions are bounded by the approved scopes and the connected user's Retool organization access.
05 · Monitoring, approval, and recovery
Show the Retool instance, OAuth scopes, target app or organization, resource environment, query, invite list, and build or function-run effect before consequential actions. Keep production resources separated from development and review contexts.
06 · Limits and caveats
Client setup varies: ChatGPT requires Developer mode, managed Claude organizations require an owner-installed connector, and self-hosted Retool requires version 4.0.0 or later plus the new app-building requirements.
First-party access
Documented surfaces
Configured database SQL ↗Retool can run SQL through customer-configured database resources. Authority derives from each resource's credentials and Retool permissions; this is not access to Retool's own platform database.Source: Retool SQL clientMCP / agent surface ↗Verified first-party provider and host/client rolesAPI ↗Developer accessDeveloper docs ↗SDKs and platform guidanceProduct ↗Native platform experience
Agent access
MCP support
Official MCP server + 3rd Party MCP servicesRetool organization MCP plus MCP host/agent capabilitiesCurrent documented service
Support: Official MCP server + 3rd Party MCP services
Read scope: Inspect apps and build activity, function runs, organization users and access, audit logs, connected resources, and environment configurations.
Write scope: Import or build apps, cancel failed builds, review function runs, execute resource-backed analysis queries, bulk-invite users, and manage pending invites.
Authentication: OAuth 2.0 with a consent flow for selecting requested scopes.
Approval boundary: Confirm app imports or builds, resource queries, function-run review decisions, bulk invitations, and pending-invite changes with the target instance and environment visible.
Protocol does not erase product boundaries.
Confirm the current tool catalog, plan, region, scopes, rate limits, terms, and write behavior before implementation.
Editorial assessment
Access-maturity dimensions
A comparative architecture lens—not a quality score, market ranking, or buying recommendation. Scale: 1–5.
Data access4
Action access4
Event access4
Identity4
Governance4
Agent access3
UI extensibility4
Portability3
Observability4
Documentation4
Proposed customer-shaped experiences
What customers could create on top.
The output could be an export, report, graph, artifact, application, agent, workflow, or downstream feed. These proposals are derived from documented access—not claims that Retool ships them.
Single-platform patterns
- Rapid customer-owned operational application shell
- BYO-UI application shell
- Capability gateway
- Agent and tool operations console
Multi-platform compositions
- Retool + systems of record: byo-ui application shell
- Retool + systems of production + systems of engagement: cross-system decision workspace
Evidence and dates
First-party references, with publisher and review dates separated
“Publisher updated” is shown only when the page exposes an update date. “BYO-UI reviewed” records when this research checked the reference. A missing publisher date is reported as missing—not replaced with the review date.
5 recorded sources
MCP / agent-role validationRepresentative source
https://docs.retool.com/org-users/guides/mcp ↗Retool documents a public-beta provider for organization resources and app building, while Retool Agents can also consume external MCP servers.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 10, 2026
Targeted first-party MCP/agent-role review; broader API inventory retained
APISource inventory
https://docs.retool.com/api ↗First-party API reference.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 10, 2026
Inventory source: structurally normalized; content was not individually reopened in this pass.
Developer docsSource inventory
https://docs.retool.com/ ↗First-party platform documentation.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 10, 2026
Inventory source: structurally normalized; content was not individually reopened in this pass.
HomepageSource inventory
https://retool.com/ ↗Product overview.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 10, 2026
Inventory source: structurally normalized; content was not individually reopened in this pass.
Configured database SQLTargeted review
Retool SQL client ↗Retool can run SQL through customer-configured database resources. Authority derives from each resource's credentials and Retool permissions; this is not access to Retool's own platform database.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 10, 2026
Targeted first-party access review
Verified fact
Tied to cited first-party evidence reviewed for this profile.
Source inventory
Official links recorded for deeper research but not necessarily reopened endpoint by endpoint.
Editorial assessment
System role, maturity interpretation, and architectural boundary.
Proposed design
Interface patterns and compositions—not vendor product claims.