Is Supabase MCP safe?
Supabase MCP Server is a database MCP server. This is its security and risk review — what it can access, what that means for your team, and how to audit every MCP server your engineers run.
Supabase MCP can modify data and local state.
It can change or delete data it has access to. Scope its credentials to the minimum it needs and audit it before granting access to production databases or systems of record.
What Supabase MCP can access
Handles credentials
Requires API keys or tokens; mishandling can leak secrets.
Reads databases
Queries connected databases.
Writes databases
Can modify or delete database records.
Classification is based on the server's category, published install command (stdio transport), and documented behavior. Source is public — verify the version you install matches the reviewed source.
Frequently asked
Is Supabase MCP safe to use?
Supabase MCP Server is classified as Read / write — it can modify data and local state. It can change or delete data it has access to. Scope its credentials to the minimum it needs and audit it before granting access to production databases or systems of record.
What can the Supabase MCP server access?
It has the following capabilities: handles credentials, reads databases, writes databases.
How do I know which MCP servers my team has installed?
Most teams don't — MCP servers are configured per-machine with no central record. The free CuratedMCP Auditor CLI scans a developer machine in about 60 seconds and lists every MCP server across Claude Code, Cursor, Windsurf, and Copilot, flagging credential leaks and filesystem access. Run: npx @curatedmcp/auditor
Security reviews for similar servers
Risk classifications are maintained by CuratedMCP's catalog review.