Firestore, browsable at last.
REST-backed document browsing and editing with SQL-like and JSON query workflows, cursor pagination, schema analysis, and emulator endpoint support.
REST API · emulator support · OAuth tokens
What Mongrel does when you run a Firestore query.
Click any step below to see what happens between the query tab and the documents grid. Same execution path the workbench uses.
// Paged Fetch · orders
Reads the orders collection through the REST documents endpoint in pageSize batches, following nextPageToken until the query's limit is covered. No composite index required.
// orders · project prod-app-e2f1 · SQL query tab SELECT * FROM orders WHERE status = 'paid' AND createdAt > '2026-06-01' ORDER BY createdAt DESC LIMIT 20 // GET /v1/projects/prod-app-e2f1/databases/(default)/documents/orders?pageSize=300 // ← documents[] + nextPageToken · filter, sort, and limit applied locally // ✓ no composite index required // …or written as a JSON query object: { "collection": "orders", "filter": { "$and": [ { "status": "paid" }, { "createdAt": { "$gt": "2026-06-01" } } ] }, "sort": { "createdAt": -1 }, "limit": 20 }
What Mongrel ships for Firestore.
Document browser
Collections, subcollections, and documents in a tree. Edit fields in place with correct Firestore value types.
JSON query editor
Write queries as native JSON objects - filter, sort, projection, and limit - with the same operators as the SQL surface.
SQL-like queries
A familiar SELECT-style surface over collections - WHERE, ORDER BY, and LIMIT parsed into Mongrel's Firestore document query path.
Collection stats
Sample-based document counts and storage sizes per collection - Firestore's REST API exposes no MongoDB-style collection metadata.
Cursor pagination
Page large collections with continuation tokens. Forward and backward paging without pulling the whole collection.
Schema analysis
Sample documents per collection to infer field types and coverage, and flag inconsistent document shapes.
Emulator support
Point Mongrel at a local Firestore emulator endpoint. Same workbench against localhost or production projects.
OAuth tokens
Connect with a bearer OAuth token, or no auth at all against an emulator. Tokens are stored in the OS keychain.
Export results
Export the current page of any query or browse view to JSON, CSV, Excel, or Parquet - with optional PII redaction.