Agents run read-only SQL to answer data questions without touching production write paths.
Database
Supabase MCP server
Give AI agents governed access to the Supabase MCP server through one audited gateway. Scoped permissions, full observability, and tamper-evident logs on every tool call.
What is the Supabase MCP server?
The Supabase MCP server is an open Model Context Protocol (MCP) server that connects AI agents to your Supabase Postgres database, storage, and project configuration. Through it an agent can run queries, read and write rows, and inspect schema without bespoke integration code, while the Averta MCP Gateway keeps every query scoped and audited.
supabase-execute-sql
Run SQL queries against the Postgres database.
supabase-list-tables
List tables and their schemas.
supabase-query-table
Read rows from a table with filters.
supabase-insert-row
Insert new rows into a table.
supabase-update-row
Update existing rows by primary key.
supabase-create-table
Create tables with columns and constraints.
supabase-manage-storage
List and manage storage buckets and objects.
supabase-get-logs
Read project and query logs for debugging.
Why the Averta MCP Gateway
Centralized governance
Unified authentication, audit logging, and rate control for every Supabase MCP connection.
Observability and control
Real-time visibility into usage, anomalies, and SLA compliance across every request.
One-click deployment
Enable the Supabase MCP server for your AI teams through one governed gateway, with no manual setup.
Enterprise hardening
High availability, security, and compliance alignment turn MCP from a developer utility into production-grade infrastructure.
OAuth and SSO enforcement
Enterprise authentication and SSO applied automatically to every Supabase endpoint.
Shared and per-user auth
Configure service accounts or per-user access, with secrets protected and centralized revocation.
One managed endpoint
Connect agents to Supabase through a single governed endpoint instead of locally run servers, improving your security posture.
Granular tool access control
Allow only the tools each role needs. Enable read-only access and block write tools like create and delete.
Works with every major AI platform
ChatGPT
Gemini
Mistral
Claude Code
Cursor
Windsurf
Cognition
OpenCode
Continue
Manus
Hermes
Lindy
OpenClaw
Your ownBuilt for enterprise teams.
Cloud, private VPC, embedded SDK, or gateway integration. Run Averta where your data, policies, and auditors need it.
Cloud (SaaS)
Fully managed by Averta. Fastest path to production, no infrastructure to run.
Private / VPC
Deploy in your own environment, so data never leaves your boundary.
Embedded SDK & Proxy
Drop Averta into your stack at the SDK or proxy layer, wherever your agents run.
Gateway Integration
Route agent traffic through the gateway, so policy and audit apply at the edge.
Supabase MCP use cases
Where teams put the Supabase MCP server to work, governed end to end through the Averta MCP Gateway.
Supabase MCP · Analytics queriesHow many signups by plan did we get last month?
YouRan a read-only query on the users table and grouped by plan.
- Running a read-only query
- Grouping by plan
All actions logged and governed
Powering safe AI execution at leading teams.
Cyfrin secures its production AI agents with Averta.
Book a demo“Averta gave our agents enforceable boundaries for the dev environment, so instructions like ‘don’t read .env files’ became policy instead of polite suggestions.”
Mikhail Karan
Head of Engineering
Explore other MCP servers
Browse all
Postgres MCP server
Database
Give AI agents governed access to the Postgres MCP server through one audited gateway. Scoped permissions, full observability, and tamper-evident logs on every tool call.
Airtable MCP server
Database
Give AI agents governed access to the Airtable MCP server through one audited gateway. Scoped permissions, full observability, and tamper-evident logs on every tool call.
Stripe MCP server
Payments
Give AI agents governed access to the Stripe MCP server through one audited gateway. Scoped permissions, full observability, and tamper-evident logs on every tool call.
Slack MCP server
Communication
Give AI agents governed access to the Slack MCP server through one audited gateway. Scoped permissions, full observability, and tamper-evident logs on every tool call.
HubSpot MCP server
Sales and CRM
Give AI agents governed access to the HubSpot MCP server through one audited gateway. Scoped permissions, full observability, and tamper-evident logs on every tool call.
Google Drive MCP server
Productivity
Give AI agents governed access to the Google Drive MCP server through one audited gateway. Scoped permissions, full observability, and tamper-evident logs on every tool call.
Zapier MCP server
Automation
Give AI agents governed access to the Zapier MCP server through one audited gateway. Scoped permissions, full observability, and tamper-evident logs on every tool call.
Supabase MCP server, answered
Security and setup questions teams ask before connecting the Supabase MCP server to AI agents.
Yes. The Averta MCP Gateway sits between your AI agents and any MCP server, giving each agent scoped, per-agent permissions, applying allow, escalate, or block policies on every tool call, and recording a tamper-evident audit of every action. The “Why the Averta MCP Gateway” section on this page covers what it enforces.
It is as safe as the controls around it. The server can run SQL and read and write rows through one connection, so unscoped access is the real risk. The Averta MCP Gateway enforces read-only or per-table limits and records every query.
By default it can reach the tables, storage, and configuration the connection is granted, including write and schema operations. Restricting it to read-only or specific tables is a governance decision.
Apply tool-level policy through the Averta MCP Gateway so read queries run automatically while writes, schema changes, and deletes escalate for approval. Every statement is logged.
Route agents through Averta's MCP Gateway for scoped per-agent permissions, tool-level policy, and tamper-evident audit across every Supabase action.
Yes. Supabase publishes an official MCP server (the @supabase/mcp-server-supabase package). Whichever server you run, routing it through the Averta MCP Gateway is what gives each agent scoped access and a tamper-evident audit trail.
Supabase's server can run read-only so agents query without writing. The Averta MCP Gateway takes that further with per-tool and per-table policy, so reads run automatically while writes, schema changes, and deletes escalate for approval, all logged.
Any MCP-compatible client, including Claude Code, Cursor, and Codex, can connect to the Supabase MCP server. Pointing those clients at the Averta MCP Gateway instead of the raw server adds scoped permissions, approval policies, and a tamper-evident log without changing the client setup.
See Averta OS in action
Book a demo and see how Averta OS secures your AI agents from input to execution.
Book a demo