01 · Records and state owned
Organization, users, resources, apps, and supported Retool metadata.
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
Organization, users, resources, apps, and supported Retool metadata.
03 · Actions and write paths
Build, import, and publish apps and perform supported organization/app operations.
04 · Authentication and permissions
OAuth scopes Retool organization, user, resource, and app permissions are inherited.
05 · Monitoring, approval, and recovery
Consequential writes should require explicit review; use vendor confirmation controls where available. Public beta; app publishing and organization-level actions require explicit approval and environment separation.
06 · Gaps and implementation limits
Public beta; app publishing and organization-level actions require explicit approval and environment separation.
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 guidanceEvents / extensions ↗Webhooks, apps, or extensionsProduct ↗Native platform experience
Agent access
MCP and adjacent posture
Verified first-party provider and host/client rolesRetool organization MCP plus MCP host/agent capabilitiesPublic beta
Role: dual
Read scope: Organization, users, resources, apps, and supported Retool metadata.
Write scope: Build, import, and publish apps and perform supported organization/app operations.
Authentication: OAuth scopes
Approval boundary: Consequential writes should require explicit review; use vendor confirmation controls where available.
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 interfaces
What customers could build on top.
These are design proposals derived from documented access—not claims that Retool ships these experiences.
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.
6 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
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.
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.
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.
EmbeddingSource inventory
https://docs.retool.com/apps/guides/embed ↗First-party embedded-app guidance.
- 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 the representative first-party source or targeted access review.
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.