AI agent'ların Firestore, Auth, Storage ve Functions ile etkileşime girmesine olanak tanıyan, Firebase emülatörleri için yüksek performanslı bir yerel alternatif sunar.
Ayrıca bilinen adı firenook-dev/firenook
- Yıldızlar
- 106
- Araçlar
- 55
- İndirmeler, 30 gün
- —
- En son sürüm
- 0.2.5
- Son commit
- 14 Kas 2026
- Lisans
- Apache-2.0
Firenook MCP nedir?
AI agent'ların Firestore, Auth, Storage ve Functions ile etkileşime girmesine olanak tanıyan, Firebase emülatörleri için yüksek performanslı bir yerel alternatif sunar. 55 araç sunar; örneğin firenook_status, emulators_export, firestore_get.
Özet, projenin README dosyasından oluşturuldu
Firenook MCP sunucusu hakkında
Firebase uygulamaları geliştiren yazılımcılar; Firestore, Auth, Storage ve Functions testleri için yüksek performanslı bir yerel ortam çalıştırmak amacıyla Firenook'u kullanabilirler. Resmi Firebase Local Emulator Suite yerine doğrudan kullanılabilir; bu sayede mevcut firebase.json, SDK'lar ve port ayarlarınızı korurken çok daha hızlı yazma hızları ve daha düşük bellek kullanımı elde edebilirsiniz. Sistem, yerel Rust servisleri ile inşa edilmiştir ve çalışması için Node 22, 24 veya 26 gerektirir.
Bunu bir AI kodlama agent'ı ile entegre etmek için firenook mcp komutunu kullanabilirsiniz. Bu, Claude Code, Cursor veya VS Code gibi araçların yerel backend'inizle doğrudan etkileşime girmesine olanak tanır. Sunucu; Firestore, kullanıcı token'ları, loglar, fonksiyon çağrıları, Security Rules kararları, Storage, Pub/Sub, Cloud Tasks ve Eventarc yönetimi için özel araçlar sağlar. Kurulum sırasında Java veya ek ağır bağımlılıklara ihtiyaç duymayacak şekilde hafif bir yapıda tasarlanmıştır.
Neler yapabilirsiniz
- 1Backend testlerini AI ile otomatize edinYerel ortamları hata ayıklamak için bir AI agent'a Firestore verilerini ve fonksiyon loglarını inceleme yeteneği verin.
- 2Yerel geliştirme döngülerini hızlandırınYoğun iş yükleri sırasında daha hızlı yazma ve daha düşük bellek tüketimi sağlamak için standart Firebase emülatörlerinin yerine kullanın.
- 3Kalıcı yerel verileri koruyunBir AI'ya, farklı çalışma oturumları arasında durumunu koruyan yerel bir veritabanını yönetmesi talimatını verin.
- 4Yeni projeleri hızlıca başlatınBir agent'tan sıfırdan eksiksiz bir yerel emülasyon ortamı kurmasını isteyin.
Projenin README dosyasından alınmıştır. Her kullanım durumu, oradaki bir alıntı ile kontrol edilir.
Firenook MCP nasıl yüklenir
Biçimler 10 Kas 2026 tarihinde doğrulandıCursor'a ekleGoose'a ekleFirenook MCP'yi Claude Code içine yükleyin
$ claude mcp add firenook -- npx -y firenook mcpFirenook MCP'yi Cursor içine yükleyin
~/.cursor/mcp.json
{
"mcpServers": {
"firenook": {
"command": "npx",
"args": [
"-y",
"firenook",
"mcp"
]
}
}
}Firenook MCP'yi VS Code içine yükleyin
.vscode/mcp.json
{
"servers": {
"firenook": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"firenook",
"mcp"
]
}
}
}Firenook MCP'yi VS Code CLI içine yükleyin
$ code --add-mcp '{"name":"firenook","type":"stdio","command":"npx","args":["-y","firenook","mcp"]}'Firenook MCP'yi Claude Desktop içine yükleyin
claude_desktop_config.json
{
"mcpServers": {
"firenook": {
"command": "npx",
"args": [
"-y",
"firenook",
"mcp"
]
}
}
}Firenook MCP'yi Codex içine yükleyin
$ codex mcp add firenook -- npx -y firenook mcpFirenook MCP'yi Codex config.toml içine yükleyin
~/.codex/config.toml
[mcp_servers.firenook] command = "npx" args = ["-y", "firenook", "mcp"]
Firenook MCP'yi Gemini CLI içine yükleyin
$ gemini mcp add -s user firenook npx -- -y firenook mcpFirenook MCP'yi Gemini settings.json içine yükleyin
~/.gemini/settings.json
{
"mcpServers": {
"firenook": {
"command": "npx",
"args": [
"-y",
"firenook",
"mcp"
]
}
}
}HostedMCP tarafından 16 Kas 2026 tarihinde başlatıldı
Bu komutu firenook 0.2.5 için ağsız ve anahtarsız, yalıtılmış bir konteynerde çalıştırdık. Yanıt verdi ve 55 araç listeledi.
Firenook MCP araçları 55
Sunucudan tools/list ile okundufirenook_statusThe running Firenook suite: how the project was found, hub locator, hub status, the emulators listing (host and port per service) and the CLI version; with no project, the suites whose locators answer.
emulators_exportExport the running Firestore, Auth and Storage data to a directory outside the project (firenook emulators:export).
firestore_getRead one Firestore document by path (collection/document[/subcollection/document]); returns its fields as plain JSON or exists:false.
firestore_queryRun a structured query over one collection, or with collectionGroup over every collection with that id (Firestore runQuery): optional where filters, ordering and limit; returns matching documents as plain JSON.
firestore_countCount the documents of a collection, or with collectionGroup of every collection with that id, that match optional where filters (a COUNT aggregation; no documents are read back).
firestore_setWrite a Firestore document from plain JSON: replaces it, or with merge:true updates only the given top-level fields.
firestore_deleteDelete a document (recursive:true also its subcollections) or a collection (its documents; recursive:true everything beneath) through the emulator delete route.
firestore_list_collectionsList collection ids at the database root or under a document (listCollectionIds).
firestore_missing_indexesThe indexes production would refuse the app's queries for: each one a query needed that its database's index file (firestore.indexes.json) does not declare, with the entry to add under indexes or fieldOverrides, the first query that needed it (fields and operators, no values), how many did and when; saving the file puts it in force at once.
auth_list_usersList Auth emulator accounts (accounts:batchGet) with uid, email, phone, display name, claims and provider data.
auth_get_userLook up one Auth account by uid, email or phone number (accounts:lookup).
auth_create_userCreate an Auth emulator account with a synthetic email/password, phone number or display name (never real credentials).
| firenook_status | The running Firenook suite: how the project was found, hub locator, hub status, the emulators listing (host and port per service) and the CLI version; with no project, the suites whose locators answer. | |
| emulators_export | Export the running Firestore, Auth and Storage data to a directory outside the project (firenook emulators:export). | |
| firestore_get | Read one Firestore document by path (collection/document[/subcollection/document]); returns its fields as plain JSON or exists:false. | |
| firestore_query | Run a structured query over one collection, or with collectionGroup over every collection with that id (Firestore runQuery): optional where filters, ordering and limit; returns matching documents as plain JSON. | |
| firestore_count | Count the documents of a collection, or with collectionGroup of every collection with that id, that match optional where filters (a COUNT aggregation; no documents are read back). | |
| firestore_set | Write a Firestore document from plain JSON: replaces it, or with merge:true updates only the given top-level fields. | |
| firestore_delete | Delete a document (recursive:true also its subcollections) or a collection (its documents; recursive:true everything beneath) through the emulator delete route. | |
| firestore_list_collections | List collection ids at the database root or under a document (listCollectionIds). | |
| firestore_missing_indexes | The indexes production would refuse the app's queries for: each one a query needed that its database's index file (firestore.indexes.json) does not declare, with the entry to add under indexes or fieldOverrides, the first query that needed it (fields and operators, no values), how many did and when; saving the file puts it in force at once. | |
| auth_list_users | List Auth emulator accounts (accounts:batchGet) with uid, email, phone, display name, claims and provider data. | |
| auth_get_user | Look up one Auth account by uid, email or phone number (accounts:lookup). | |
| auth_create_user | Create an Auth emulator account with a synthetic email/password, phone number or display name (never real credentials). |
55 aracın tümünü gösterDaha az araç göster
auth_delete_userDelete one Auth emulator account by uid (accounts:delete).
auth_oob_codesThe pending out-of-band codes (email verification, password reset, sign-in links) the Auth emulator holds instead of sending email.
auth_verification_codesThe pending phone verification codes the Auth emulator holds instead of sending SMS.
auth_mint_tokenMint a Firebase ID token (valid one hour) and refresh token for an existing Auth emulator user, so an agent can call a function or the REST API as that user; claims replace the custom claims for this token only.
auth_set_claimsSet an Auth emulator user's custom claims: replace them (as the Admin SDK's setCustomUserClaims does) or with mode merge change only the given keys (a null value removes that key).
auth_remove_claimsRemove the named custom claim keys from an Auth emulator user, keeping its other claims.
auth_disable_userDisable an Auth emulator account: its sign-ins and token refreshes fail until it is enabled again.
auth_enable_userEnable a disabled Auth emulator account again.
auth_revoke_tokensRevoke an Auth emulator user's refresh tokens (validSince moves to now), so its existing sessions must sign in again.
auth_list_tenantsList the Auth emulator's tenants (multi-tenancy) with their user counts and sign-in settings.
storage_listList Storage objects and folder prefixes under a prefix (one level, like listAll).
storage_get_metadataThe metadata of one Storage object (content type, size, timestamps, custom metadata, download tokens) or exists:false.
storage_readRead a Storage object's content: text inline (text, JSON, XML, SVG...), anything else as base64; at most maxBytes are returned and truncated says whether there is more.
storage_uploadUpload (create or replace) a Storage object from text or base64 bytes with a content type and custom metadata, as the Admin SDK would (rules skipped; finalize triggers run).
storage_deleteDESTRUCTIVE: delete one Storage object, or with a path ending in / every object under that folder.
storage_copyCopy a Storage object (or a folder, a path ending in /) to a new path, in the same or another bucket; refuses to overwrite unless overwrite is true.
storage_moveMove (rename) a Storage object or a folder (a path ending in /), in the same or another bucket; refuses to overwrite unless overwrite is true.
functions_listThe functions loaded by the running suite: name, region, generation, trigger kind, event type or schedule, and the HTTPS URL of request/callable functions.
functions_invokeInvoke a loaded function: an HTTPS/callable request with data, or with eventData a background event (Firestore before/after, Storage object, Pub/Sub message, Auth user, schedule, Eventarc custom event, task queue payload) shaped as the official functions shell sends it.
functions_list_callsRecent function calls, newest first: trigger kind and cause, outcome (succeeded, failed, timedOut, crashed...), HTTP status, duration and the first line of the error.
functions_get_callOne function call in full: its cause, request (method, path, headers, body), response (status, body), event payload, the error with its stack trace, the call's console output and timings.
functions_replay_callRun a recorded function call again with the same request or event (after a fix, say) and report the new call: outcome, status, response body and its id for functions_get_call.
logs_searchSearch the suite's log (every emulator and every function's console output) by service, level, function, call, text and time; returns the newest matching lines, oldest first.
logs_facetsCount the log lines matching a filter by level, service, function, codebase, extension instance and kind, to see where errors and warnings come from before reading them.
rules_getThe Security Rules in force: the Firestore rules of a database and the Storage rules of a bucket (source, whether they are enforced, the file and its problems).
rules_evaluateAsk the rules in force (or a draft) whether a request would be allowed: get, list, create, update or delete on a Firestore path or Storage object as a given user or unauthenticated; returns the verdict, the rule line that decided it and each evaluated expression's value. Nothing is written.
rules_list_denialsRecent requests the Security Rules denied (app clients only; admin and owner requests skip the rules), newest last; with explain, the rule lines that denied each one.
pubsub_publishPublish a message to a Pub/Sub emulator topic: string data as given, other JSON as its text (base64-encoded on the wire), plus attributes.
pubsub_list_topicsThe Pub/Sub emulator's topics with their published counts, subscriptions and the functions they trigger (schedule topics included).
pubsub_list_subscriptionsEvery Pub/Sub subscription (of every topic, and detached ones) with its delivery type, filter, dead-letter topic and backlog.
pubsub_peekPeek at a subscription's backlog in delivery order without pulling, leasing or acking anything: each message's state, attempts, attributes and data.
tasks_statsQueue statistics of the Cloud Tasks emulator (queueStats).
tasks_listThe Cloud Tasks queues (with their pending and running counts) and the tasks waiting in them; with queue, only that queue's tasks, optionally in one state.
tasks_runDispatch one waiting Cloud Tasks task now instead of at its schedule time (it is sent on the next tick).
schedules_listThe scheduled functions (onSchedule, pubsub.schedule): expression, time zone, next runs, paused state and the latest runs with their delivery.
schedules_runRun a scheduled function now: publish one tick to its schedule topic, as Cloud Scheduler would, and report the run.
eventarc_publishPublish a custom CloudEvent to an Eventarc channel (default the project's Firebase channel), as getEventarc().channel().publish() does, and report which functions received it and how each call ended.
eventarc_list_eventsThe Eventarc events the suite received, newest first (custom events, replays and the Firebase services' own), with how many functions matched, received or failed each.
eventarc_get_eventOne Eventarc event with its attributes, data and every function delivery (outcome, duration, invocation id for functions_get_call).
eventarc_replay_eventDeliver a received Eventarc event again to the functions it matches (a new event, origin replay) and report the new deliveries.
extensions_listThe Firebase Extensions instances the suite runs: reference and version, state (running, loading, failed) with the load error, and their function count.
extensions_reloadReload one Extensions instance (re-read its .env parameters and source, restart its functions) and report its state and functions afterwards.
emulators_clearDESTRUCTIVE: delete all data of the chosen services (every Firestore document, every Auth user and tenant, every Storage object, every Pub/Sub topic, subscription, schema and message, every Cloud Tasks task and its history). Clearing more than one service needs confirmProject set to the project id.
| auth_delete_user | Delete one Auth emulator account by uid (accounts:delete). | |
| auth_oob_codes | The pending out-of-band codes (email verification, password reset, sign-in links) the Auth emulator holds instead of sending email. | |
| auth_verification_codes | The pending phone verification codes the Auth emulator holds instead of sending SMS. | |
| auth_mint_token | Mint a Firebase ID token (valid one hour) and refresh token for an existing Auth emulator user, so an agent can call a function or the REST API as that user; claims replace the custom claims for this token only. | |
| auth_set_claims | Set an Auth emulator user's custom claims: replace them (as the Admin SDK's setCustomUserClaims does) or with mode merge change only the given keys (a null value removes that key). | |
| auth_remove_claims | Remove the named custom claim keys from an Auth emulator user, keeping its other claims. | |
| auth_disable_user | Disable an Auth emulator account: its sign-ins and token refreshes fail until it is enabled again. | |
| auth_enable_user | Enable a disabled Auth emulator account again. | |
| auth_revoke_tokens | Revoke an Auth emulator user's refresh tokens (validSince moves to now), so its existing sessions must sign in again. | |
| auth_list_tenants | List the Auth emulator's tenants (multi-tenancy) with their user counts and sign-in settings. | |
| storage_list | List Storage objects and folder prefixes under a prefix (one level, like listAll). | |
| storage_get_metadata | The metadata of one Storage object (content type, size, timestamps, custom metadata, download tokens) or exists:false. | |
| storage_read | Read a Storage object's content: text inline (text, JSON, XML, SVG...), anything else as base64; at most maxBytes are returned and truncated says whether there is more. | |
| storage_upload | Upload (create or replace) a Storage object from text or base64 bytes with a content type and custom metadata, as the Admin SDK would (rules skipped; finalize triggers run). | |
| storage_delete | DESTRUCTIVE: delete one Storage object, or with a path ending in / every object under that folder. | |
| storage_copy | Copy a Storage object (or a folder, a path ending in /) to a new path, in the same or another bucket; refuses to overwrite unless overwrite is true. | |
| storage_move | Move (rename) a Storage object or a folder (a path ending in /), in the same or another bucket; refuses to overwrite unless overwrite is true. | |
| functions_list | The functions loaded by the running suite: name, region, generation, trigger kind, event type or schedule, and the HTTPS URL of request/callable functions. | |
| functions_invoke | Invoke a loaded function: an HTTPS/callable request with data, or with eventData a background event (Firestore before/after, Storage object, Pub/Sub message, Auth user, schedule, Eventarc custom event, task queue payload) shaped as the official functions shell sends it. | |
| functions_list_calls | Recent function calls, newest first: trigger kind and cause, outcome (succeeded, failed, timedOut, crashed...), HTTP status, duration and the first line of the error. | |
| functions_get_call | One function call in full: its cause, request (method, path, headers, body), response (status, body), event payload, the error with its stack trace, the call's console output and timings. | |
| functions_replay_call | Run a recorded function call again with the same request or event (after a fix, say) and report the new call: outcome, status, response body and its id for functions_get_call. | |
| logs_search | Search the suite's log (every emulator and every function's console output) by service, level, function, call, text and time; returns the newest matching lines, oldest first. | |
| logs_facets | Count the log lines matching a filter by level, service, function, codebase, extension instance and kind, to see where errors and warnings come from before reading them. | |
| rules_get | The Security Rules in force: the Firestore rules of a database and the Storage rules of a bucket (source, whether they are enforced, the file and its problems). | |
| rules_evaluate | Ask the rules in force (or a draft) whether a request would be allowed: get, list, create, update or delete on a Firestore path or Storage object as a given user or unauthenticated; returns the verdict, the rule line that decided it and each evaluated expression's value. Nothing is written. | |
| rules_list_denials | Recent requests the Security Rules denied (app clients only; admin and owner requests skip the rules), newest last; with explain, the rule lines that denied each one. | |
| pubsub_publish | Publish a message to a Pub/Sub emulator topic: string data as given, other JSON as its text (base64-encoded on the wire), plus attributes. | |
| pubsub_list_topics | The Pub/Sub emulator's topics with their published counts, subscriptions and the functions they trigger (schedule topics included). | |
| pubsub_list_subscriptions | Every Pub/Sub subscription (of every topic, and detached ones) with its delivery type, filter, dead-letter topic and backlog. | |
| pubsub_peek | Peek at a subscription's backlog in delivery order without pulling, leasing or acking anything: each message's state, attempts, attributes and data. | |
| tasks_stats | Queue statistics of the Cloud Tasks emulator (queueStats). | |
| tasks_list | The Cloud Tasks queues (with their pending and running counts) and the tasks waiting in them; with queue, only that queue's tasks, optionally in one state. | |
| tasks_run | Dispatch one waiting Cloud Tasks task now instead of at its schedule time (it is sent on the next tick). | |
| schedules_list | The scheduled functions (onSchedule, pubsub.schedule): expression, time zone, next runs, paused state and the latest runs with their delivery. | |
| schedules_run | Run a scheduled function now: publish one tick to its schedule topic, as Cloud Scheduler would, and report the run. | |
| eventarc_publish | Publish a custom CloudEvent to an Eventarc channel (default the project's Firebase channel), as getEventarc().channel().publish() does, and report which functions received it and how each call ended. | |
| eventarc_list_events | The Eventarc events the suite received, newest first (custom events, replays and the Firebase services' own), with how many functions matched, received or failed each. | |
| eventarc_get_event | One Eventarc event with its attributes, data and every function delivery (outcome, duration, invocation id for functions_get_call). | |
| eventarc_replay_event | Deliver a received Eventarc event again to the functions it matches (a new event, origin replay) and report the new deliveries. | |
| extensions_list | The Firebase Extensions instances the suite runs: reference and version, state (running, loading, failed) with the load error, and their function count. | |
| extensions_reload | Reload one Extensions instance (re-read its .env parameters and source, restart its functions) and report its state and functions afterwards. | |
| emulators_clear | DESTRUCTIVE: delete all data of the chosen services (every Firestore document, every Auth user and tenant, every Storage object, every Pub/Sub topic, subscription, schema and message, every Cloud Tasks task and its history). Clearing more than one service needs confirmProject set to the project id. |
Otomatik kontroller
Çalıştırıldı 16 Kas 2026Tam rapor →Henüz doğrulanmadı. Bir sunucunun 80 puana, ciddi bir bulgu olmamasına ve kontrol edebilmemiz için yeterli veriye ihtiyacı vardır. Kontroller nasıl çalışır · Daha fazla puan için nelerin düzeltileceği
- Kaynak deposu bağlantılı ve erişilebilirfirenook-dev/firenook is public and reachablegithub.com/firenook-dev/firenook ↗Geçti
- Paket, bu depoyu kaynağı olarak gösteriyorfirenook names firenook-dev/firenook as sourcenpmjs.com/package/firenook ↗Geçti
- Derleme kökeni (Sigstore onayı)Sigstore attestation for firenooknpmjs.com/package/firenook/v/0.2.5#provenance ↗Geçti
- Açık kaynak lisansı (OSI)Apache-2.0spdx.org/licenses/Apache-2.0.html ↗Geçti
- Son bir yıl içinde commit veya sürüm mevcutLast commit or release 2026-11-14github.com/firenook-dev/firenook ↗Geçti
- OpenSSF ScorecardKontrol edilmedi
- Paket adı popüler bir pakete yakın değilNo popular package one edit away from firenookGeçti
- Pakette veya bağımlılıklarında kritik uyarı yokthe package checked; no critical advisoryosv.dev ↗Geçti
- Modele yönelik gizli talimat yokA tool description points at credential filesBulgu
- Yıkıcı araçlar etiketlenmişNo tool named like delete, drop or execGeçti
- Uzak uç nokta MCP el sıkışmasına yanıt veriyorKontrol edilmedi
Already using the Firebase emulators? Install Firenook and change one word:
npm install --save-dev firenook
- firebase emulators:start --import ./data
+ firenook emulators:start --import ./data
Same flags, same ports, and your firebase.json, rules, Functions code and app
stay as they are. In a terminal, run it as npx firenook emulators:start. To
keep your data between runs, add --keep-data.
Firenook needs Node 22, 24 or 26. Starting a new project? npx firenook init
sets one up on one screen, installs it and starts the emulators.
Why Firenook
- A drop-in for the official emulator. It reads
firebase.json,.firebaserc, rules and indexes the way the Firebase CLI does, serves the same ports, and your client and Admin SDKs connect unchanged. It imports and exports the official format. - Fast and light. Native Rust services with the data on disk. On a real application's two-hour workload, Firenook peaked at 2.11 GiB of memory where the official emulator reached 22.57 GiB, answered writes in 5.1 ms against 208 ms at the median, and used 61% less CPU.
- Your data stays. Add
--keep-dataand Firestore, Auth and Storage come back with all your data in about half a second, even with millions of documents. A crash loses at most the last second of writes. - Nothing else to install. No Java, no firebase-tools, nothing else downloaded at install or start (an Extension from the registry is fetched once, on first use). npm or Bun picks the native engine for your machine; Node runs your Functions.
- A console and a terminal made for it, and
firenook mcpfor your coding agent: Firestore, users and their tokens, logs and function calls, Security Rules decisions, Storage, Pub/Sub, Cloud Tasks and Eventarc as tools.npx firenook mcp addsets it up for Claude Code, Cursor and VS Code; other agents run the samenpx firenook mcp.
Switching from the official emulator
Keep firebase-tools for deploying, and add .firenook/ to your .gitignore:
every run keeps its working data there.
$ npx firenook init --adopt --dry-run
skip Firenook: firebase.json configures the hosting emulator, which Firenook does not implement; skipping it.
ok nothing to change; services: firestore, auth, storage, functions
- "emulators": "firebase emulators:start --import ./data --export-on-exit",
+ "emulators": "firenook emulators:start --import ./data --export-on-exit",
Same flags, same ports, the official export format both ways. To keep your
data between runs without exporting, replace --export-on-exit with
--keep-data; ./data is then never written.
Starting fresh instead: npx firenook init.
Getting started
covers both.
The console
The console the Firebase emulators should have had. Google's Emulator UI
has no page for your Functions, Pub/Sub, Cloud Tasks or Eventarc, only a log.
Firenook's console covers every service it runs, live, on the Emulator UI's
port, at
http://127.0.0.1:4000/console. It shows every function call with its
trigger, duration and logs, and an inbox of the codes and links Auth would
have sent. It has Firestore and Storage with their rules, Pub/Sub, Cloud
Tasks and Eventarc, and an Overview of every service's health.
What it emulates
Firestore, Authentication, Cloud Storage (with native Security Rules), Cloud
Functions (every trigger type, reload on save, debugging), Extensions, Pub/Sub,
Cloud Tasks and Eventarc. Realtime Database, Hosting, App Hosting and Data
Connect are not emulated; a firebase.json that configures them still starts,
with a warning. See compatibility.
Benchmarks
One real application with 211,205 documents and 6.7 GB in Storage, and two hours of its traffic against each emulator in turn on one server. Firenook answered 25 of the 26 query shapes faster and tied on the last. The method and every figure.
Commands
firenook init [--yes] # a new project: choose, install, start
firenook init --adopt [--dry-run] # adapt an existing firebase.json
firenook doctor # read-only checks, JSON
firenook emulators:start [options] # --only, --project, --import, --export-on-exit, --inspect-functions
firenook emulators:start --keep-data [--import ./seed] # keep data between runs, in .firenook/state
firenook emulators:start --build # compile TypeScript first and on every save
firenook emulators:exec "npm test" # start, run your tests, stop
firenook emulators:export ./export # snapshot a running suite
firenook functions:invoke NAME [--data JSON | --event-data JSON] # call any function, any trigger
firenook ext:vendor [--offline] # copy registry Extensions into the project
firenook mcp # the running suite as tools for a coding agent
firenook mcp add # give Claude Code, Cursor and VS Code that server
firenook state:inspect | state:compact --state-dir DIR
Every command and option: CLI reference.
Requirements
Node 22, 24 or 26 on macOS (Apple silicon or Intel), Linux (x64 or arm64,
glibc 2.28 or newer: RHEL 8, Debian 10, Ubuntu 20.04, node:24-slim and later;
not Alpine) or Windows x64; your Functions run on it, and a codebase whose
engines.node asks for another Node is warned about at start. Keep optional
dependencies enabled: they carry the native engine for your platform. Commit
your lockfile and upgrade on purpose.
License
Apache License 2.0. Firebase, Cloud Firestore, Cloud Functions, Cloud Storage, Cloud Pub/Sub and Cloud Tasks are trademarks of Google LLC; Firenook is not affiliated with or endorsed by Google.
Firenook MCP soruları
Firenook MCP'yi Claude Code'a nasıl eklerim?
Terminalinizde claude mcp add firenook -- npx -y firenook mcp komutunu çalıştırın. Her projede kullanılabilir olması için --scope user ekleyin.
Firenook MCP'yi Cursor'a nasıl eklerim?
~/.cursor/mcp.json dosyasını açın ve yukarıdaki yükleme bölümünde gösterilen Cursor yapılandırmasını kullanarak sunucuyu mcpServers altına ekleyin.
Firenook MCP hangi araçları sunar?
55 araç sunar; bunlar arasında firenook_status, emulators_export, firestore_get, firestore_query, firestore_count yer alır.
Firenook'u mevcut Firebase yapılandırmamla kullanabilir miyim?
Evet, mevcut firebase.json, .firebaserc, kurallar ve indekslerinizi okuyan doğrudan kullanılabilir bir alternatiftir.
Firenook'un çalışması için Java gerekiyor mu?
Hayır, Firenook yerel Rust servislerini kullanır; Java veya firebase-tools gerektirmez.
AI kodlama agent'ımı Firenook'a nasıl bağlayabilirim?
firenook mcp komutunu kullanarak Claude Code, Cursor veya VS Code gibi agent'lara Firestore, kullanıcılar, loglar ve fonksiyon çağrıları gibi araçlar sağlayabilirsiniz.