Skip to content
Custom Connectors
SolutionsConnectorsPricingResourcesBlog
Build my connector

Connect Firebase to Claude Code

Let Claude create and update documents in your Firebase databases. From the terminal, inside the sessions where you already work.

Build my connectorTalk to us

How do you connect Firebase to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect Firebase, you add a Firebase MCP server: a small hosted service that exposes Firebase's data and actions over the Model Context Protocol. With a custom connector we build for you, that is one command in the terminal, then an OAuth sign-in with your own Firebase account. No API keys pasted into config files.

claude mcp add --transport http firebase https://your-connector-url/mcp

Then run /mcp inside a Claude Code session to sign in. Add it with --scope project and the connector is checked into the repo for your whole team.

What can Claude Code do in Firebase once connected?

Full read-write Firebase access lets Claude create documents, update specific fields, and adjust records in Firestore or the Realtime Database from a request, then surface what changed for your approval. The lookups and manual edits that used to mean opening the console happen where the data already lives.

  • Create a new document in a Firestore collection from a structured request
  • Update specific fields on an existing document without overwriting the rest
  • Set or merge a value at a path in the Realtime Database
  • Run a filtered query and propose batched edits across the matching documents
  • Soft-delete or flag a record so it stays recoverable after you approve
  • Move a document between collections while preserving its fields

One connector, every Claude surface

The connector we build is a remote MCP server, which is the same standard claude.ai and Claude Desktop use. Add it once and the same Firebase access works in Claude Code for you, in claude.ai for the rest of the team, and in Claude Desktop. One build, one set of permissions, one monthly plan covering all of them.

Build it yourself, or have it built?

If you live in the terminal, you can absolutely write your own MCP server against the Firebase API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when Firebase changes its API and when the MCP spec itself moves, and scoping write actions so an agent can never do more than you intended. We build Firebase connectors with separated read and write tools and approval gates on destructive actions, then host and maintain them so they keep working while you work.

Frequently asked questions

Does the same Firebase connector work in claude.ai and Claude Code?
Yes. It is one remote MCP server. Claude Code adds it with a single "claude mcp add" command; claude.ai and Claude Desktop add it as a custom connector in Settings. Each person signs in with their own Firebase account, so access always matches what that person can already see and do.
Do I need to host or maintain anything myself?
No. The connector runs as a hosted service we operate: we handle uptime, token health, API changes on Firebase's side, and MCP spec migrations under the monthly plan. Your side is one command in the terminal and an OAuth sign-in.
Is it safe to give a coding agent write access to Firebase?
Write access is scoped, not blanket. Read tools and write tools are separated, destructive actions like deleting or sending are gated behind your explicit approval, and the connector can never exceed the permissions of the Firebase account it signs in with. Revoking access is one click in Firebase.

More on the Firebase connector

Firebase connector for claude.aiAmazon Redshift + Claude CodeLooker + Claude CodeMetabase + Claude Code

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.

Build my connectorTalk to us