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.

DimensionFirebase MCP ServerMCP server that lets AI assistants work directly with Firebase servicesMCP Toolbox for DatabasesGoogle's official database MCP toolbox — define AI-accessible database tools via config
FMRS54 / 100 · D74 / 100 · B
Reliability9 / 2013 / 20
Security and permissions6 / 2013 / 20
Maintenance11 / 2017 / 20
Documentation15 / 2016 / 20
Setup experience13 / 2015 / 20
Best for
  • Developers with data already in Firebase who want AI assistants to read and write it directly
  • Users of MCP clients such as Claude Desktop, Cursor, VS Code, or Augment Code
  • Workflows combining document database, file storage, and user lookup
  • 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 without a Firebase project or service account credentials
  • Firebase administration tasks such as project management or function deployment
  • Environments without an MCP client or the ability to configure environment variables
  • 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 Firebase service account private key JSON file (SERVICE_ACCOUNT_KEY_PATH)
  • The service account must have proper permissions for Firestore, Storage, and Authentication services
  • Requires a Firebase Storage bucket name, either configured or defaulted
  • 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
  • Service account private keys carry broad privileges; misconfiguration or leakage can expose full data access
  • AI assistants can delete Firestore documents and upload/overwrite storage files, creating risk of unintended operations
  • The firestore_list_collections tool may trigger a Zod validation error in client logs (a known MCP SDK issue that does not affect functionality but may cause confusion)
  • Some Firestore queries require manually creating composite indexes in the Firebase Console
  • 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 clientsClaude Desktop, Augment Code, VS Code, CursorClaude Code, Gemini CLI, Zed, Antigravity
Tools120