M
MCP Directory CURATED DIRECTORY
911 MCP servers indexed
中文
← Back to directory
COMPARE UP TO 4 SERVERS

Compare MCP servers

Compare scores, permissions, risks, and fit in one decision-focused table.

DimensionQuery MCPSafely manage Supabase through chat.MCP Toolbox for DatabasesGoogle's official database MCP toolbox — define AI-accessible database tools via config
FMRS50 / 100 · D74 / 100 · B
Reliability8 / 2013 / 20
Security and permissions12 / 2013 / 20
Maintenance5 / 2017 / 20
Documentation14 / 2016 / 20
Setup experience11 / 2015 / 20
Best for
  • Supabase developers using Cursor, Windsurf, Cline, or Claude Desktop.
  • Teams that want SQL, project management, authentication administration, and logs in one interface.
  • Development environments using local Supabase or Supabase.com-hosted projects.
  • Teams that want precise control over which database operations an AI can perform, rather than open arbitrary SQL execution
  • Scenarios needing a unified MCP setup across multiple database engines
Not for
  • Users who need self-hosted Supabase support.
  • Users who need custom connection strings or Session Pooling.
  • Production teams that require ongoing maintenance, official support, or the latest features.
  • Local-only Supabase users who need Management API or Auth Admin features.
  • Lightweight cases that just want to run a few ad-hoc SQL queries without maintaining a tools.yaml config (a simpler single-database MCP may be a better fit)
Required permissions
  • Requires a database project reference and database password.
  • All operations require a QUERY_API_KEY from thequery.dev.
  • Management API operations require a Supabase personal access token.
  • Auth Admin operations require a Supabase service role key.
  • Database connections use transaction pooling; remote projects require the correct Supabase region.
  • Database credentials (username/password/connection string) are supplied via env vars or config
  • A tool's actual permission is whatever SQL statement is defined in tools.yaml — designed for least privilege, but misconfiguration can still over-expose access
Risks and side effects
  • Safe mode permits only low-risk read-only operations by default.
  • Write operations require unsafe mode, and high-risk operations also require explicit confirmation.
  • Extreme-risk operations, such as deleting a project, are blocked.
  • Automatically generated migrations do not eliminate the risk of incorrect SQL or data loss when using high-privilege credentials.
  • The service role key and database password are highly sensitive credentials.
  • The project is no longer actively maintained, and the README points users to Supabase's official MCP server.
  • If tools.yaml defines SQL statements that allow unconstrained writes or deletes, the AI could accidentally modify data
  • The prebuilt toolsets (--prebuilt) favor convenience and may expose broader query capability than a specific business actually needs — use a custom tools.yaml in production
Supported clientsCursor, Windsurf, Cline, Claude DesktopClaude Code, Gemini CLI, Zed, Antigravity
Tools130