Gleap AI agents can use Supabase through Composio, for teams that build on Supabase and receive bug reports from customers in Gleap. Kai Code, Kai Support and custom agents can check the data, schema and logs behind a report with read-only access, while schema changes stay in a pull request your engineers review.
What a Gleap agent can do in Supabase
- The data behind a report: Execute read-only database query runs a SELECT as Supabase’s read-only user, for example to check the record a customer says shows the wrong value.
- Schema for a fix: Get Table Schemas and Generate TypeScript types give Kai Code the columns and types it needs when a fix touches the database.
- Logs around the report: Get project logs reads API, database and Edge Function logs around the time a Gleap bug report arrived.
- Edge Function code: Retrieve a function body shows the deployed source of an Edge Function that a report points to.
Example: an invoice total that shows zero
A customer reports through the Gleap widget that a new invoice shows a total of zero. Kai Support investigates the ticket with Supabase enabled in Kai Code’s MCP settings, runs a read-only query on the invoice and finds a missing tax rate, then traces the calculation in the code and prepares a coding task. Kai Code starts it on its own when you allow it, or a teammate does, and checks the table schema while it prepares a pull request with a fix and a test. Your engineers review and merge it.
How to connect Supabase
- In Gleap, open Kai Code, click Settings and open MCP.
- Click Add MCP server, search for “Supabase” and select it.
- Click Connect Supabase and follow the authorization Gleap shows: approve access in the Supabase sign-in window, or enter a Supabase access token if the form asks for one.
- Open the Supabase server and switch off the tools Kai Code should not call, such as Execute project database query, Apply a database migration and the function deploy and delete actions.
- For a custom agent, add Supabase under the agent’s Tools with Add tool instead, then publish and test it.
Kai Code is on Team, Pro and Enterprise, and Kai Support can use connected apps as tools on the same plans. Custom agents are on the Team, Pro and Enterprise plans.
FAQ
Does Gleap integrate with Supabase?
Yes. Kai Code, Kai Support and custom agents use Supabase through Composio’s Supabase toolkit, which supports OAuth and access tokens. They query Supabase only while they run; Gleap does not copy your database.
Does Gleap connect to Supabase through MCP?
Yes. Gleap connects to Composio’s MCP server for Supabase with the Supabase account you connect, and the agent calls only the actions you leave switched on. To use a different remote MCP server, add it by URL: as a Custom MCP tool for Kai Support or a custom agent, or as a custom HTTP server in Kai Code.
What can a Gleap AI agent do in Supabase?
It can list projects, tables, functions, branches and migrations, read schemas, logs and advisors, run read-only or full SQL queries, apply migrations and deploy, invoke or delete Edge Functions. For investigation, read-only queries and logs are enough; leave writes to your engineers.
Which Gleap plan includes the Supabase integration?
Kai Code and Kai Support’s investigations can use Supabase on Team, Pro and Enterprise, and Kai Support can use connected apps as tools in its customer conversations on the same plans. Custom agents that use Supabase are part of the Team, Pro and Enterprise plans. The connected Supabase account decides which projects the agents reach. AI usage is billed separately; see pricing.
Should an agent query production data?
Only with read-only access and only for the data a report is about. Keep Execute project database query off, tell the agent which tables it may read, and review its first runs.
