Inspect Supabase projects, schemas, logs, and Edge Functions from the terminal
Connect Supabase and your agent can look at the projects it is authorized for: project settings and API URLs, development branches, Edge Function source, storage configuration, advisory notices, and generated TypeScript types. Questions about a project get answered from the project itself. Running SQL against the database is a separate, previewed step.
21 tools: 20 read, 1 write. Reads answer instantly. Writes require approval by default. Everything is logged.
What a governed Supabase Read MCP run looks like inside Luumen.
Authorize once with OAuth 2.0. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.
Read actions answer immediately. Anything that writes — execute sql — is shown as a plan and requires approval by default, including the 1 action classified as destructive. Administrators configure that per tool, so you decide exactly which actions can ever run unattended.
You decide. Actions are granted per agent, skill, and team, and per environment — production is not staging. Read access can be broad while writes stay narrow.
Every call to Supabase Read MCP — read or write, approved or declined — is recorded with the actor, the input, and the result, and can be linked to the ticket or change record.
Connect in minutes. Every action scoped, approved, and audited from day one.