Does Retool integrate with Supabase MCP?
Partial — Agents support MCP, but Supabase MCP OAuth is reported broken
Partially. Retool Agents can connect to remote MCP servers as tools over HTTP or SSE using OAuth, Basic or Bearer auth, so the mechanism exists. But for Supabase's hosted MCP specifically, community users report Retool's OAuth request includes extra parameters that Supabase's MCP rejects, so authorization fails. As of late 2025 this was unresolved, with no official fix.
| Integration method | MCP server resource (Retool Agents) — Retool Agents can add a remote MCP server as a tool, with OAuth 2.0, Basic auth or Bearer token, over Streamable HTTP or SSE. The mechanism works in general, but for Supabase's hosted MCP specifically, community users report Retool's OAuth request includes extra parameters (access_type, audience, prompt) that Supabase's MCP rejects, so authorization fails. |
|---|---|
| Sync direction | Intended two-way once connected: a Retool Agent would call Supabase MCP tools to read and modify Supabase data on demand. In practice, the reported OAuth failure blocks the connection from completing for the hosted Supabase MCP. |
| Plan required | Requires access to Retool Agents (Retool's agent feature). The MCP tool connection itself supports OAuth, Basic and Bearer auth. No specific paid tier is documented for adding an MCP tool beyond having Agents available. |
| Setup time | ~15 minutes unverified estimate |
How to connect Retool to Supabase MCP
- Open or create a Retool Agent and go to the Configuration tab.
- Choose "Add new tool" then "Connect to MCP Server".
- Create a new MCP server resource and paste the remote server URL.
- Select the auth method (OAuth 2.0, Basic, or Bearer token) and add credentials.
- Authenticate when prompted — note that the hosted Supabase MCP currently rejects Retool's OAuth parameters, so this step is where the reported failure occurs.
Known friction points
- Connecting Retool Agents to Supabase's hosted MCP fails during OAuth: Retool's request includes access_type, audience and prompt, and Supabase's MCP returns "Unrecognized key(s) in object: 'access_type', 'prompt', 'audience'". Reported by multiple users from late October 2025 and still open through late December 2025, with no official fix. [source]
- Retool's MCP tool connection only supports remote-hosted MCP servers (Streamable HTTP or SSE); local stdio servers must be exposed via an HTTP gateway, and tool execution is capped at 2 minutes. [source]
FAQ
- Can Retool Agents use Supabase's MCP server?
- Partially. Retool Agents support adding remote MCP servers as tools, but community users report that connecting to Supabase's hosted MCP fails at the OAuth step because Supabase rejects extra parameters Retool sends. As of late 2025 it was unresolved.
- What exactly breaks when connecting Supabase MCP to Retool?
- Retool's OAuth request includes access_type, audience and prompt, and Supabase's MCP returns an "Unrecognized key(s)" error rather than ignoring them, so authorization cannot complete.
- Is there a workaround?
- No confirmed fix as of late 2025. Retool mentioned possibly supporting custom auth flows for MCP resources in future, but nothing was shipped in the reported thread.
✓ Last verified: 2026-06-10 · Every claim on this page links to a primary source. If the integration changed, the page is out of date — check the sources below.
Sources
- Retool Community — Anyone tried connecting Supabase MCP? (#62838) (accessed 2026-06-10)
- Retool Docs — Connect an agent to an MCP server (accessed 2026-06-10)
- Retool Blog — Retool MCP server (accessed 2026-06-10)