Supabase MCP Server

Supabase's MCP server enables AI agents to manage PostgreSQL databases, execute SQL queries, inspect table schemas, and interact with Supabase storage and edge functions. It allows agents to query database records, generate schema migrations, analyze relational data structures, automate backend operations, and create development branches.

Start for free

Supabase MCP Server

Benefits with Ory + Supabase MCP Server

Supabase's MCP server gives your agents access to your Supabase projects, including the Postgres schema, SQL execution, migrations, logs, edge functions, and storage. One misdirected SQL statement or migration can alter production data. Ory Agent Security lets schema reviewers read structure and logs while SQL and deployments stay with the agents you approve, and every tool call is attributed to the user and agent behind it.

View documentation

Use Cases

— 01 use case

Agent IAM

Schema reviewers at Read, branch experimenters at Write, the few agents that run SQL or migrations at Admin, and Block for everyone else.

Explore Agent IAM

Core Functionality

— 04 capabilities

Read, write, admin, or no access
Ory Agent Security classifies every tool on the Supabase MCP server as read, write, or admin, so you can give each user, team, or agent type only the level it needs: read for schema review agents, write for agents managing development work, admin for a migration agent owned by the database's maintainers, and no access for agents that should never reach your databases.
Enforced before execution
Ory Agent Security checks each tool call against the user, the agent acting for them, and any sub-agent inside the agent harness, so a denied SQL statement stops before it reaches Supabase, with nothing to roll back and no gateway to deploy.
Observe, then enforce
Observe mode shows which agents run SQL or deploy functions and for whom without blocking anything, so you can apply Ory's pre-built policy for the Supabase MCP server and enforce it on your own schedule.
Complete audit trail
Every allow and deny decision on the Supabase MCP server streams to your SIEM through OpenTelemetry with the user, agent, and action attached, so you can show which agent ran a statement against your database and on whose behalf.