How is this different from connecting Supabase MCP directly?

Connected directly, an agent sees every tool the server exposes and holds the credential itself. Through TrustGate you choose which tools each agent gets, and every call is logged against the agent that made it.

What if the Supabase MCP API changes?

We track the Supabase MCP schema, so the tool catalogue stays current. Tools you have already allowed keep working, and anything new stays denied until you enable it.

Can I give different agents different Supabase tools?

Yes. Access is set per agent: one can get a handful of read tools, another the full set. You grant the whole MCP or single tools within it.

Where can I see what my agents did in Supabase?

Every call is logged against the agent that made it, with the tool it used. Activity can be sent on to your own monitoring.

Do I need to run the Supabase MCP server myself?

No. TrustGate connects to the Supabase MCP server and sits in front of it. Your agent only talks to your TrustGate URL, never to Supabase directly.

Connect Supabase MCP to your AI agents, securely.

Q: Is Supabase MCP secure?

The server itself exposes 40 tools, and some of them can write to your Supabase account. Behind TrustGate an agent only sees the tools you allow, requests and responses are inspected, and every call is logged. Anything outside the allowlist is denied before it reaches Supabase.

One secured endpoint for every Supabase call your AI agents make, scoped per user, inspected, and logged.

Get started for free

Get a demo

Try Supabase MCP now

What your agents can ask once Supabase MCP is connected.

Select the tools your AI agents can call

40 tools from the Supabase MCP schema.

Showing 40 tools

list_tablesreadLists all tables within the specified schemas.
list_extensionsreadLists the available and installed Postgres extensions.
list_migrationsreadLists the database migrations applied to the project.
apply_migrationhigh riskApplies a SQL migration to the database. Use this instead of execute_sql for DDL operations.
execute_sqlhigh riskExecutes raw SQL in the Postgres database. Destructive statements prompt for confirmation outside read-only mode.
get_project_urlreadGets the API URL for a Supabase project.
list_projectsreadLists all Supabase projects for the user.
get_projectreadGets the details for a Supabase project.
create_projecthigh riskCreates a new Supabase project. This incurs cost and prompts for confirmation.
pause_projecthigh riskPauses a Supabase project, taking its database offline.
restore_projectwriteRestores a paused Supabase project.
list_organizationsreadLists the organizations the user belongs to.
get_organizationreadGets the details of an organization, including its plan.
submit_feedbackwriteSends feedback about Supabase tools to the Supabase team.
delete_feedbackwriteDeletes feedback sent with submit_feedback. Pass the same project_id used to submit it.
get_publishable_keysreadGets all publishable API keys for a project, including legacy anon keys (JWT-based) and modern publishable keys (format: sb_publishable_...).
get_costreadGets the cost of creating a new project or branch. Never assume organization as costs can be different for each. Always repeat the cost to the user and confirm their understanding before proceeding.
confirm_costreadReturns a confirmation ID for the cost of a new project or branch returned by `get_cost`.
list_edge_functionsreadLists all Edge Functions in a Supabase project.
get_edge_functionreadRetrieves the file contents for an Edge Function.
deploy_edge_functionwriteDeploys an Edge Function to a Supabase project.
create_edge_function_secretwriteCreates or updates an Edge Function secret for the project. The user enters the value in the Supabase dashboard; it never passes through the AI client.
create_branchwriteCreates a development branch on a Supabase project. Requires a paid plan and incurs cost.
list_branchesreadLists all development branches of a Supabase project.
merge_branchwriteMerges a development branch back into production.
reset_branchhigh riskResets a development branch, discarding its changes.
rebase_branchwriteRebases a development branch on production.
delete_branchwriteDeletes a development branch.
get_logsreadGets logs for a Supabase project by service type: api, postgres, edge functions, auth, storage or realtime.
get_advisorsreadGets the advisory notices for a Supabase project, covering security and performance.
query_logsreadRuns a custom read-only SQL query against a Supabase project's logs.
search_docsreadSearches the Supabase documentation using GraphQL.
generate_typescript_typesreadGenerates TypeScript types based on the database schema.
list_storage_bucketsreadLists all storage buckets in a Supabase project.
get_storage_configreadGet the storage config for a Supabase project.
update_storage_configwriteUpdate the storage config for a Supabase project.
create_notebookwriteCreates a saved notebook shared with everyone who has access to the Supabase project.
list_notebooksreadLists the notebooks in a Supabase project. Notebook bodies are omitted — use get_notebook to read a specific notebook.
get_notebookreadGets a notebook from a Supabase project, including its cells.
run_notebookhigh riskRuns every database and log query cell in a saved notebook, in order, and returns each cell's rows or error.

What Supabase MCP exposes

Supabase MCP groups its 40 tools into 8 categories, each with a suggested starting policy.

All 40 tools as JSON, ready to paste.

Category	Covers	Access	Suggested policy
Database	Tables, columns, extensions, migrations and raw SQL execution	Read / Write	Run in read-only mode where possible; approve migrations and destructive SQL
Projects	Project listing, details, creation, pause, restore and configuration	Read / Write	Approve project creation; it incurs cost
Edge Functions	Listing, reading and deploying Edge Functions	Read / Write	Require approval before deploying
Branches	Development branch creation, listing, merge, reset, rebase and deletion	Read / Write	Approve merges and resets; branching requires a paid plan
Monitoring	Service logs and advisory notices for security and performance	Read	Treat log output as potentially sensitive
Docs & Types	Documentation search and TypeScript type generation from the schema	Read	Allow documentation searches
Storage	Listing storage buckets and reading or updating the storage configuration	Read / Write	Approve storage configuration changes
Notebooks	Creating, listing and reading saved notebooks and running their SQL cells	Read / Write	run_notebook can run mutating SQL; require approval

Connect Supabase MCP to your AI agent

Four steps, under ten minutes.

01
Sign in to NeuralTrust
Open the NeuralTrust platform, sign in and go to Getting started, then Connect your tools.
02
Choose your agent
When asked which agent you use, pick Claude Code, Codex, Cursor, Windsurf, Copilot or your own code.
03
Connect Supabase
Find Supabase in the tool list and connect it.
04
Connect your agent
Follow the steps on screen to add the config to your agent, then send the test prompt.

Permissions down to the single tool

You do not allow Supabase MCP or block it. You allow the exact tools each agent can call, one by one.

Supabase MCP	40 TOOLS AVAILABLE
Code review agent	4 tools, read only
Issue triage bot	9 tools
Platform team assistant	all 40 tools

Tool by toolConnecting the server is not the unit of access. Each tool is granted on its own.
Default denyA tool you have not enabled is never exposed to the agent.
Approval on writesTools that change or delete things can require a human to confirm.

Is Supabase MCP secure?

One endpoint instead of raw credentials. Every call is checked against policy and logged.

AI agentsConnect through your MCP client configuration.	NeuralTrustApply controls based on your configuration.	Supabase MCP40 documented tools.
Coding assistants	Connection & credentialsper user	Projects12 tools
Internal copilots	Tool access policiesdeny by default	Database6 tools
Workflow automations	Request & response inspectioninline	Branches6 tools
Compatible MCP clients	Activity monitoringalerts and logs	All other tools16 tools