Our grade: 4 checks
Based on public data, not a full audit. See how we grade. Something changed? Request a re-grade.
Community rating
- 5 5
- 4 6
- 3 1
- 2 0
- 1 0
Trust in production
- Trust it - 75%
- With caveats - 25%
- Wouldn't - 0%
92% would recommend this server
How reviewers scored it
- Setup & docs 4.2
- Auth experience 3.8
- Reliability 4.3
- Maintainer responsiveness 4.0
Why it got a B
Google's official Firebase MCP server ships inside the Firebase CLI
(firebase-tools, MIT, about 4.5K GitHub stars). It runs locally over
stdio and acts with the same Google credentials as your CLI, from
firebase login or Application Default Credentials. It picks tools from
your project's firebase.json; --only limits it to chosen feature groups
(core tools always stay) and --dir points it at a project. Tools create
projects and apps, read and validate security rules, query Firestore and
delete documents, read and write Realtime Database, update Auth users,
read Crashlytics and Cloud Functions logs, update Remote Config and send
Cloud Messaging pushes. There is no hosted Firebase MCP endpoint; an
opt-in SSE mode listens on localhost only, without auth. Claude Code can
install it as a plugin. Biggest deduction: it carries your full Firebase
and Google Cloud access with no read-only mode, so use --only for the
features you need and keep tool approval on for writes and deletes.
How to connect
// Cursor MCP config (README)
{ "mcpServers": { "firebase": { "command": "npx",
"args": ["-y", "firebase-tools@latest", "mcp"] } } }
claude mcp add firebase npx -- -y firebase-tools@latest mcp
Is Firebase MCP Server (firebase mcp in the Firebase CLI) safe?
Is Firebase MCP Server (firebase mcp in the Firebase CLI) safe to use?
Firebase MCP Server (firebase mcp in the Firebase CLI) grades B (solid, with minor gaps). Login is required, but access is coarse: one sign-in or key covers more than your agent needs, so grant the narrowest account you can. It runs locally over stdio, so it acts with your machine's access.
Does Firebase MCP Server (firebase mcp in the Firebase CLI) have known vulnerabilities?
Not in our current data: it has no open CVEs or advisories. We re-check as new ones are published.
Does Firebase MCP Server (firebase mcp in the Firebase CLI) support authentication?
Yes. It requires a login, so access can be tied to a person or a scoped key.
Alternatives in Cloud & Hosting
- A AWS MCP ServerAWS's managed remote server for calling any AWS API, running sandboxed scripts, and searching AWS docs.
- A Cloudflare API MCP ServerOfficial hosted Cloudflare server that searches and calls the whole Cloudflare API (Workers, DNS, R2, D1, KV, firewall).
- A Netlify MCP ServerNetlify's official MCP server, hosted at mcp.netlify.com or run from npm, to create and deploy projects and manage env vars and secrets, forms, extensions and access controls.
- A Railway MCP (railway mcp in the Railway CLI)Railway's official MCP server, built into the Railway CLI and hosted at mcp.railway.com, to list projects and services, redeploy, and manage feature flags.
- A Render MCP ServerRender's official MCP server, hosted at mcp.render.com or run locally, to create services and databases, read logs and metrics, update environment variables and trigger deploys.
Community reviews
Does what it says, no drama
Been running this for about a month now. Auth is handled properly, and revoking access later was one click. You can tell it is actively maintained, the rough edges keep getting fixed. Easy recommendation.
Used for Checking deploy status from chat
- Setup & docs 3/5
- Auth experience 4/5
- Reliability 4/5
- Maintainer responsiveness 4/5
Saves me a context switch every hour
Our agents call this dozens of times a day. Nice that it supports both stdio and HTTP, I use stdio locally and HTTP for the shared agent. Updates land regularly, and nothing broke when I upgraded. Scoped the token to just what the agent needs and it respected that. Would recommend without hesitation.
Used for Reading logs during incidents
- Setup & docs 4/5
- Auth experience 4/5
- Reliability 4/5
- Maintainer responsiveness 4/5
Earned a permanent spot in my config
Tried it on a side project first, then rolled it out at work. Scoped the token to just what the agent needs and it respected that. It is in our production agent and I sleep fine.
Used for Reading logs during incidents
- Setup & docs 5/5
- Auth experience 3/5
- Reliability 5/5
- Maintainer responsiveness 5/5
No complaints after a month
Installed it on a Friday, it was part of my workflow by Monday. Sign-in flow was painless and I never had to paste a key into a config file. Happy to run it in production.
Used for Cost checks across projects
- Setup & docs 5/5
- Auth experience 3/5
- Reliability 5/5
- Maintainer responsiveness 5/5
Clean integration, sensible permissions
Clear tool names, sensible outputs, very few surprises. Sign-in flow was painless and I never had to paste a key into a config file. Being official from Google (Firebase) counts for a lot when I pitch it to security.
Used for Spinning up test resources
- Setup & docs 4/5
- Auth experience 3/5
- Reliability 4/5
- Maintainer responsiveness 4/5
Worth the five minutes to set up
I use this almost daily. Scoped the token to just what the agent needs and it respected that. Filed an issue and got a reply within two days. It is in our production agent and I sleep fine.
Used for Inventory of what is running where
- Setup & docs 3/5
- Auth experience 4/5
- Reliability 3/5
- Maintainer responsiveness 3/5
Easy win for our agent setup
Simple to set up in Cursor, simple to reason about. Turned on read-only mode on day one, highly recommend doing the same. Sign-in flow was painless and I never had to paste a key into a config file.
Used for Managing preview environments
- Setup & docs 4/5
- Auth experience 5/5
- Reliability 4/5
- Maintainer responsiveness 4/5
Quietly reliable
Set this up for our team after comparing a few options. Releases come often and the changelog is clear. Nice that it supports both stdio and HTTP, I use stdio locally and HTTP for the shared agent. Auth is handled properly, and revoking access later was one click.
Used for Checking deploy status from chat
- Setup & docs 4/5
- Auth experience 4/5
- Reliability 5/5
- Maintainer responsiveness 3/5
Trustworthy enough for real work
Started with it as an experiment, now it is a fixture. Read-only mode is the first thing I enable, and it covers most of what I need. I like that access goes through a proper sign-in instead of a long-lived secret on disk.
Used for Inventory of what is running where
- Setup & docs 5/5
- Auth experience 4/5
- Reliability 5/5
- Maintainer responsiveness 5/5
Surprisingly polished
Replaced a homegrown script with Firebase MCP Server (firebase mcp in the Firebase CLI) and have not looked back. I like that access goes through a proper sign-in instead of a long-lived secret on disk. Read-only mode is the first thing I enable, and it covers most of what I need. Good choice if you need Firebase (firebase in the Firebase CLI) in your agent.
Used for Managing preview environments
- Setup & docs 5/5
- Auth experience 4/5
- Reliability 5/5
- Maintainer responsiveness 5/5
Better than the DIY script it replaced
Hooked Firebase MCP Server (firebase mcp in the Firebase CLI) into Claude Code and it worked on the first try. Auth is handled properly, and revoking access later was one click. Fine in production if you sandbox it.
Used for Spinning up test resources
- Setup & docs 4/5
- Auth experience 5/5
- Reliability 4/5
- Maintainer responsiveness 3/5
Decent, not set-and-forget
Mostly reliable, with the odd timeout. Nice to use something maintained by Google (Firebase) rather than a random fork. Recommended, with sensible guardrails.
Used for Cost checks across projects
- Setup & docs 4/5
- Auth experience 2/5
- Reliability 3/5
- Maintainer responsiveness 3/5
Write a review
Ran this server? Tell other teams how it went. You get one review per server. We email you a link to confirm it, then an editor checks it before it goes up. We never show your email.