SkillFoxx

Firenook MCP

Firenook replaces the Firebase emulator with a fast native engine and gives agents MCP access to Firestore, Auth and Storage.

  • 106 ★ on the repository
  • Last commit
  • Apache-2.0
MCP server

Extended access

Why this level

  • The agent can write and delete documents, users and files in the emulator, recursively too.
  • Calls carry the owner token and bypass Security Rules.
All reasons and checks

firenook-dev/firenookAuthor:firenook-dev

Install

In your terminal, with SkillFoxx CLI

npx skillfoxx add mcp/firenook

Detects the agents on your machine, shows the access level and pins the version.

Other ways to install

Access and checks

How we review

Extended accessThe tool runs code or makes network calls and only reads external data.

  • The agent can write and delete documents, users and files in the emulator, recursively too.
  • Calls carry the owner token and bypass Security Rules.

This is third-party code. Review the repository files before installing.

What it does

Firenook is a compatible replacement for the Firebase Local Emulator Suite: it reads `firebase.json`, rules and indexes and serves Firestore, Auth, Storage, Functions, Pub/Sub, Cloud Tasks and Eventarc on the same ports. Data survives restarts with the `--keep-data` flag. `firenook mcp` starts an MCP server over stdio. The agent reads and writes Firestore documents, creates users and mints tokens for them, reads logs and every function call with its error, asks the Security Rules why a request was denied, and works with Storage files, Pub/Sub, Cloud Tasks and Eventarc. Tool groups are chosen with `--only`.

Who it is for. Developers of Firebase apps who run the local emulator and want an agent to inspect data, users and function errors on its own.

Good fit when

  • A function fails in the emulator and the agent must find the call with its stack trace.
  • A Firestore request is denied and you need to know which security rule blocks it.
  • A test needs a user with custom claims and a token to call a function as that user.
  • The Java-based Firebase emulator eats memory and loses data on stop.

Not a fit when

  • You need access to a production Firebase project: the server works only with the local suite.
  • The project relies on emulators missing from the Firenook list: check the compatibility file.
  • The agent must not modify emulator data.

Example request

Read the `orders` collection in the emulator, find orders without a `status` field and explain why the app write was rejected by the rules.

MCP

Transport
stdio
Authentication
not required

Limitations

You need Node 22, 24 or 26 and a running `firenook emulators:start`: without it the tools return a clear error. Tools marked console work only while the emulator UI is on (it is by default). Extensions from the registry are downloaded once on first use. Calls to the emulator carry the owner token used by the Admin SDK, so they bypass Security Rules. Check compatibility with your own project in `COMPATIBILITY.md`.

How to disable. Remove the `firenook` entry from `.mcp.json` or the client configuration. Stop the emulator as usual and uninstall the package with `npm uninstall firenook`.

FAQ

How do I connect the server to an agent?

Run `npx firenook mcp add` in the project folder: it writes settings for the Claude Code, Cursor and VS Code it finds. For Codex use `codex mcp add firenook -- npx firenook mcp`.

Can the agent touch production data?

No, the server sees only the local emulator suite on this machine and sends no data anywhere.

How do I restrict the tool set?

Start `firenook mcp --only firestore,auth`. The `firenook_status` and `emulators_export` tools are always available.

What if several suites are running?

Set the project explicitly with `--project <id>` or `--config /path/to/firebase.json`. Otherwise the tools name both suites and ask you to choose.

Do I need Java and firebase-tools?

No, Firenook installs as one npm package with a native engine. Keep `firebase-tools` only for the other Firebase CLI commands.

Discussion

No questions or reviews yet.

MCP servers

Firebase MCP Server

Firebase CLI and MCP Server

Official

Official Firebase MCP server from the Firebase CLI: projects, Firestore, Auth, Crashlytics, Remote Config and function logs

MCP serverBroad access4.5K
Official

FireCMS Cloud MCP server: an agent reads Firestore data, infers collection schemas and manages the project's users.

MCP serverBroad access1.3K

A DynamoDB emulator in Rust on SQLite that starts in milliseconds and runs as an HTTP server or an MCP server for agents.

MCP serverMinimal access110

An MCP server and plugin for agents that generate web APIs from OpenAPI, AsyncAPI, GraphQL, gRPC and SQL specs on a Rust core.

MCP serverExtended access123
Official

An MCP server for Lunora apps: the agent reads functions, tables, logs and errors of a deployed backend and runs queries.

MCP serverExtended access296
Official

Official Firebase plugin for agents: 14 skills on Firestore, Auth, Hosting, Crashlytics, Remote Config and security rules

PluginBroad access510

README in short

Replace the emulator with one word: `firenook emulators:start` instead of `firebase emulators:start`. For agents there are `firenook mcp` and `firenook mcp add`.

README badge

Report a problem