Official Firebase MCP server bundled with Firebase CLI, giving Claude project, app, Auth, Firestore, Realtime Database, Storage, Crashlytics, Data Connect, Functions, Messaging, Remote Config, rules, and deploy capabilities.
Firebase MCP uses the same user credentials that authorize the Firebase CLI in the environment where it runs., Tools can create Firebase projects and apps, add Android SHA hashes, inspect and update environment settings, validate and retrieve security rules, deploy resources, and check deploy status., Auth tools can retrieve users, update a user's disabled state or custom claims, and set SMS region policies., Firestore and Realtime Database tools can query, read, delete, and write data depending on the active project and credentials., Messaging and Remote Config tools can send Firebase Cloud Messaging messages and publish or roll back Remote Config templates., Crashlytics tools can inspect issues, events, notes, reports, and update issue state; Functions tools can list deployed functions and query logs.
Privacy notes
Tool results can expose Firebase project IDs, app IDs, SDK configuration, Auth user identifiers, custom claims, Firestore documents, Realtime Database paths, Storage object URLs, Crashlytics events, Functions logs, FCM targets, and Remote Config templates., Gemini in Firebase features may generate plausible but incorrect output; Firebase documentation warns to validate output and not enter personally identifiable information or user data into chat., Firebase CLI credentials, refresh tokens, service context, project aliases, and environment configuration should stay out of prompts, issues, logs, screenshots, and committed files., Storage download URLs, Crashlytics stack traces, Functions logs, database records, and Auth data may contain customer data, credentials, unreleased feature names, or production incident details.
Author
Firebase
Submitted by
oktofeesh1
Claim status
unclaimed
Last verified
2026-06-06
Decision playbook
Review trust signals before you adopt
Signals are present but mixed. Use the checklist below to confirm the source and operational safety for your environment.
Compare context
Selected
0
Current score
63
Baseline
—
Delta
No baseline selected
No major trust-signal divergence detected in the current selection.
Source and provenance checks
Needs review
Confirm ownership and provenance before trusting install instructions.
Source link availableRequired
Open the canonical repository and verify ownership.
Done
Source provenance statusRequired
Marked as source-backed.
Done
Metadata reviewed
No reviewed flag detected in metadata.
Pending
Safety and privacy checks
Complete
Validate risk disclosures before installation or API wiring.
Safety notes presentRequired
Review the listed safety guidance before running commands.
Done
Privacy notes presentRequired
Review data handling notes before connecting accounts or secrets.
Done
Trust level risk gateRequired
Trust level does not block evaluation.
Done
Package and install checks
Needs review
Check package metadata and artifact integrity signals.
Install payload available
Install or copy payload is available for review.
Done
Package verification flag
No package verification flag provided.
Pending
Checksum metadata
No checksum provided for downloaded artifact.
Pending
Compare-driven decision checks
Needs review
Use compare context to validate trade-offs before adoption.
Compare tray has multiple entries
Add at least one more entry to compare trust differences.
6 safety and 4 privacy notes across 4 risk areas. Review closely: credentials & tokens, network access.
4 areas
SafetyCredentials & tokensFirebase MCP uses the same user credentials that authorize the Firebase CLI in the environment where it runs.
SafetyGeneralTools can create Firebase projects and apps, add Android SHA hashes, inspect and update environment settings, validate and retrieve security rules, deploy resources, and check deploy status.
SafetyGeneralAuth tools can retrieve users, update a user's disabled state or custom claims, and set SMS region policies.
SafetyCredentials & tokensFirestore and Realtime Database tools can query, read, delete, and write data depending on the active project and credentials.
SafetyNetwork accessMessaging and Remote Config tools can send Firebase Cloud Messaging messages and publish or roll back Remote Config templates.
SafetyData retentionCrashlytics tools can inspect issues, events, notes, reports, and update issue state; Functions tools can list deployed functions and query logs.
PrivacyGeneralGemini in Firebase features may generate plausible but incorrect output; Firebase documentation warns to validate output and not enter personally identifiable information or user data into chat.
PrivacyCredentials & tokensFirebase CLI credentials, refresh tokens, service context, project aliases, and environment configuration should stay out of prompts, issues, logs, screenshots, and committed files.
PrivacyCredentials & tokensStorage download URLs, Crashlytics stack traces, Functions logs, database records, and Auth data may contain customer data, credentials, unreleased feature names, or production incident details.
Safety notes
Firebase MCP uses the same user credentials that authorize the Firebase CLI in the environment where it runs.
Tools can create Firebase projects and apps, add Android SHA hashes, inspect and update environment settings, validate and retrieve security rules, deploy resources, and check deploy status.
Auth tools can retrieve users, update a user's disabled state or custom claims, and set SMS region policies.
Firestore and Realtime Database tools can query, read, delete, and write data depending on the active project and credentials.
Messaging and Remote Config tools can send Firebase Cloud Messaging messages and publish or roll back Remote Config templates.
Crashlytics tools can inspect issues, events, notes, reports, and update issue state; Functions tools can list deployed functions and query logs.
Gemini in Firebase features may generate plausible but incorrect output; Firebase documentation warns to validate output and not enter personally identifiable information or user data into chat.
Firebase CLI credentials, refresh tokens, service context, project aliases, and environment configuration should stay out of prompts, issues, logs, screenshots, and committed files.
Storage download URLs, Crashlytics stack traces, Functions logs, database records, and Auth data may contain customer data, credentials, unreleased feature names, or production incident details.
Prerequisites
Node.js and npm available in the MCP client runtime.
Firebase CLI credentials for the Google account or service context Claude should use.
Firebase project selected and access scoped to the minimum roles needed for the planned work.
Team approval policy for write-capable tools such as deploys, Auth updates, database writes, messaging sends, Remote Config updates, and Crashlytics issue changes.
Privacy review before sending project data, user identifiers, crash data, logs, database records, or Gemini in Firebase prompts through the MCP client.
Firebase MCP Server is the official Firebase Model Context Protocol server
bundled with Firebase CLI. It gives Claude and other MCP clients access to
Firebase-specific project, app, Auth, database, rules, Crashlytics, App Hosting,
Data Connect, Functions, Messaging, Storage, Remote Config, and deployment
workflows through the same credentials used by the Firebase CLI.
The Firebase MCP README documents setup for Claude Code, Cursor, Windsurf,
Firebase Studio, Gemini CLI, VS Code Copilot, Cline, and other MCP clients. It
also documents server capabilities, prompts, and resources for Firebase docs and
workflow guides.
These sources were reviewed on 2026-06-06. Prefer the live Firebase docs,
MCP README, MCP metadata, package metadata, and license for current setup
commands, available tools, credential behavior, and Gemini in Firebase guidance.
Features
Official MCP server bundled with firebase-tools.
Stdio setup with npx -y firebase-tools@latest mcp.
Firebase CLI credential reuse for project access.
Project and app tools for listing, creating, inspecting, and retrieving SDK configuration.
Security rules retrieval and validation for Firebase products.
Deploy and deploy-status tools.
Firebase Auth user lookup, user update, custom-claim, disabled-state, and SMS region policy tools.
Firestore document and collection query tools.
Realtime Database read and write tools.
Storage download URL retrieval.
Crashlytics issues, events, notes, reports, and issue-state tools.
Data Connect compile, service list, and operation execution tools.
Cloud Functions listing and log retrieval.
Firebase Cloud Messaging send tool.
Remote Config template get and update tools.
Resources for Firebase docs and workflow-specific guides.
Installation
For Claude Code, the Firebase README documents an official plugin path and a
manual MCP server path. To add the MCP server manually:
claude mcp add firebase npx -- -y firebase-tools@latest mcp
Sign in with the Firebase CLI in the same environment, then verify the MCP
client shows the Firebase server as connected.
Use Cases
Ask Claude to inspect the active Firebase project and list apps before making setup changes.
Validate or retrieve security rules while reviewing Firestore, Storage, or Realtime Database access.
Query Firestore or Realtime Database during local development and debugging.
Review Crashlytics issues, events, notes, and reports before prioritizing fixes.
Retrieve Cloud Functions logs while diagnosing a backend issue.
Compile and execute Data Connect operations against a service or emulator.
Send a reviewed Firebase Cloud Messaging message to a token or topic.
Retrieve or update Remote Config templates with explicit approval.
Deploy Firebase resources only after reviewing the proposed changes and active project.
Safety and Privacy
Firebase MCP is a live cloud-service control surface. Treat it as access to the
Firebase project, not as a read-only documentation helper. Use least-privilege
Firebase roles, check the active project before every write, and require human
approval before deploys, database writes, Auth user changes, FCM sends, Remote
Config publishes, Crashlytics issue updates, or production-facing changes.
The server can expose sensitive operational and customer data. Avoid putting
credentials, tokens, PII, production records, crash details, logs, or private
project context into prompts unless the MCP client, model provider, and Firebase
data-use policy have been approved for that data. Validate Gemini in Firebase
output before applying it, and do not use untested generated code or rules in
production.
Duplicate Check
Existing entries cover related databases, Supabase, Google Cloud-style
workflows, and Firebase-alternative skills. No firebase/firebase-tools,
firebase-tools mcp, Firebase MCP Server, Firestore MCP, Firebase Auth MCP,
Crashlytics MCP, Firebase Messaging MCP, or Remote Config MCP entry was found in
content/mcp, content/tools, content/guides, content/agents, or
content/skills.
Show that Firebase MCP Server is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.
[](https://heyclau.de/entry/mcp/firebase-mcp-server)
How it compares
Firebase MCP Server side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.
Official Firebase MCP server bundled with Firebase CLI, giving Claude project, app, Auth, Firestore, Realtime Database, Storage, Crashlytics, Data Connect, Functions, Messaging, Remote Config, rules, and deploy capabilities.
Argo Project Labs MCP server for connecting Claude to Argo CD applications, clusters, managed resources, workload logs, events, sync operations, and resource actions through stdio or HTTP stream transports.
✓Firebase MCP uses the same user credentials that authorize the Firebase CLI in the environment where it runs.
Tools can create Firebase projects and apps, add Android SHA hashes, inspect and update environment settings, validate and retrieve security rules, deploy resources, and check deploy status.
Auth tools can retrieve users, update a user's disabled state or custom claims, and set SMS region policies.
Firestore and Realtime Database tools can query, read, delete, and write data depending on the active project and credentials.
Messaging and Remote Config tools can send Firebase Cloud Messaging messages and publish or roll back Remote Config templates.
Crashlytics tools can inspect issues, events, notes, reports, and update issue state; Functions tools can list deployed functions and query logs.
✓Argo CD MCP can inspect clusters, applications, resource trees, managed resources, workload logs, and resource events.
By default all tools are available; setting MCP_READ_ONLY to true disables create_application, update_application, delete_application, sync_application, and run_resource_action.
sync_application can apply changes to Kubernetes resources and may prune resources depending on options.
delete_application can remove Argo CD applications and may cascade deletion to child resources depending on options.
run_resource_action can trigger actions on resources managed by an application.
Disabling TLS certificate validation with NODE_TLS_REJECT_UNAUTHORIZED weakens transport security and should be limited to reviewed development contexts.
✓Coolify MCP Server can start, stop, restart, redeploy, cancel deployments, update env vars, create or delete projects, environments, applications, databases, services, backups, storages, scheduled tasks, private keys, GitHub apps, and cloud tokens depending on API permissions.
Batch tools such as `restart_project_apps`, `bulk_env_update`, `stop_all_apps`, and `redeploy_project` can affect multiple production services at once.
Deployment, control, backup, storage, private key, cloud token, GitHub app, and scheduled-task operations should require explicit confirmation.
Custom `--header` values may carry auth-proxy secrets; never let an agent invent, log, or modify them casually.
Test on non-production projects or staging resources before allowing Claude to operate live Coolify infrastructure.
✓DBHub can execute SQL queries against configured databases.
SQL execution can read, create, update, delete, or otherwise modify data depending on database permissions and requested queries.
Configure read-only mode, row limits, query timeouts, least-privilege credentials, and human review before using DBHub with production or sensitive databases.
Custom tools can wrap reusable parameterized SQL, so review their definitions before allowing agents to call them.
Privacy notes
✓Tool results can expose Firebase project IDs, app IDs, SDK configuration, Auth user identifiers, custom claims, Firestore documents, Realtime Database paths, Storage object URLs, Crashlytics events, Functions logs, FCM targets, and Remote Config templates.
Gemini in Firebase features may generate plausible but incorrect output; Firebase documentation warns to validate output and not enter personally identifiable information or user data into chat.
Firebase CLI credentials, refresh tokens, service context, project aliases, and environment configuration should stay out of prompts, issues, logs, screenshots, and committed files.
Storage download URLs, Crashlytics stack traces, Functions logs, database records, and Auth data may contain customer data, credentials, unreleased feature names, or production incident details.
✓Argo CD application specs, cluster names, repository URLs, revisions, namespaces, Kubernetes manifests, resource events, and workload logs can reveal secrets, internal topology, deployment history, incident details, or customer data.
ARGOCD_BASE_URL, ARGOCD_API_TOKEN, stateless HTTP request headers, cluster names, namespace names, and application names should stay out of prompts, issues, logs, screenshots, and committed files.
Workload logs and resource events may include credentials, tokens, environment variables, error traces, or production incident context.
HTTP transport should be authenticated and network-restricted so Argo CD tools are not reachable by untrusted clients.
✓Coolify access tokens, base URLs, custom headers, application UUIDs, server IPs, domains, logs, env vars, deployment logs, private keys, cloud-provider tokens, GitHub app data, team membership, backups, database metadata, and service configuration can be exposed to the MCP client.
Application and deployment logs may contain secrets, customer data, build output, container metadata, private repository details, and runtime errors.
Environment variable and cloud-token tools can reveal or mutate sensitive infrastructure credentials.
Documentation search is local to the server, but Coolify API calls contact the configured Coolify instance.
Keep tokens and auth-proxy headers in local MCP client configuration only, and avoid sharing transcripts that include infrastructure identifiers or logs.
✓Database connection strings, hostnames, schemas, table names, column names, row data, query text, query results, traces, and errors may be visible to the MCP client and model provider.
Databases can contain personal data, customer records, credentials, business metrics, audit logs, payment data, healthcare data, and proprietary operational state.
Avoid exposing production databases or regulated data unless the database, MCP client, and model session are approved for that access.
Prerequisites
Node.js and npm available in the MCP client runtime.
Firebase CLI credentials for the Google account or service context Claude should use.
Firebase project selected and access scoped to the minimum roles needed for the planned work.
Team approval policy for write-capable tools such as deploys, Auth updates, database writes, messaging sends, Remote Config updates, and Crashlytics issue changes.
Node.js 18 or newer.
Argo CD instance with API access.
Argo CD API token scoped to the minimum applications, projects, clusters, and actions Claude should use.
Read-only mode enabled unless the workflow explicitly needs application or resource mutations.
Running Coolify instance with API access enabled.
Coolify API access token scoped to the resources Claude may inspect or manage.
Node.js 20 or newer for the published npm server.
Review of which servers, projects, applications, databases, services, deployments, env vars, private keys, teams, cloud tokens, and scheduled tasks the token can access.
Node.js and npx available to the MCP client runtime.
A PostgreSQL, MySQL, MariaDB, SQL Server, or SQLite database connection.
Database credentials with the minimum privileges needed for the workflow.
Read-only permissions or DBHub guardrails configured before connecting production data.
Install
claude mcp add firebase npx -- -y firebase-tools@latest mcp