Set up the Firestore Toolbox MCP server
Firestore Toolbox is a hosted Mintive (formerly MintMCP) connector, built on Google's MCP Toolbox, that exposes document tools against a single Firestore database. You choose which tools it exposes (listing collections, reading, querying, and writing documents, and reading security rules) by declaring them in a configuration value.
Prerequisites
- A Mintive admin account
- A Google Cloud or Firebase project with a Firestore database in Native mode (Standard edition)
- Permission to create service accounts and keys in that project
Create the Firestore database
Skip this if the project already has a database.
- In the Firebase console or the Google Cloud console, open Firestore and click Create database.
- Keep the database ID
(default)and choose Standard Edition. The connector targets the native Firestore engine, and your first database is the one eligible for the free tier. - Choose Restrictive security rules. Those rules govern web and mobile SDK clients only, so they don't block the connector, which authenticates as a service account.
- Pick a location. It's permanent, so choose one close to your users (e.g.,
us-central1).
Create a service account
All users of this connector share one Google identity, so create a dedicated service account rather than reusing a personal or owner credential.
- In the Google Cloud console, go to IAM & Admin > Service Accounts and click Create service account (e.g.,
mintmcp-firestore). - Grant it the roles the tools need:
- Cloud Datastore User to read and write documents, or Cloud Datastore Viewer if the connector should only read
- Firebase Rules Viewer if you expose the
firestore-get-rulestool
- Open the service account, go to Keys > Add key > Create new key, choose JSON, and download the file. Treat it like a password.
- If you expose the rules tool, enable the Firebase Rules API under APIs & Services > Library.
If key creation fails with a policy error, your Google Cloud organization blocks service account keys (iam.disableServiceAccountKeyCreation), and an organization admin needs to allow keys for this project.
The service account's roles are the real boundary on what the connector can do. Firestore security rules don't apply to it, so a service account with Cloud Datastore User can read and write every document in the database even when the rules deny everything.
Define the tools
The connector exposes only the tools you declare in the TOOLBOX_TOOLS environment variable. Every tool runs against the database you configure in Add Firestore Toolbox to Mintive, so tools never set a source. Each tool has a kind and an optional description, and you can group tools into named toolsets.
The setup dialog pre-fills a read-only set (list_collections, get_documents, query_collection). To enable every tool on this page, replace it with the config below. The write tools need Cloud Datastore User, and the rules tools need Firebase Rules Viewer and the Firebase Rules API.
{
"tools": {
"list_collections": { "kind": "firestore-list-collections", "description": "List Firestore collections. Leave parentPath empty for root collections, or pass a document path to list its subcollections." },
"get_documents": { "kind": "firestore-get-documents", "description": "Get one or more Firestore documents by relative path, e.g. customers/abc123." },
"query_collection": { "kind": "firestore-query-collection", "description": "Query documents in a Firestore collection with optional filters, ordering and limit. Pass filters as [] and orderBy as an empty string when not needed." },
"add_documents": { "kind": "firestore-add-documents", "description": "Add a new document to a Firestore collection with an auto-generated ID." },
"update_document": { "kind": "firestore-update-document", "description": "Update fields of an existing Firestore document by relative path." },
"delete_documents": { "kind": "firestore-delete-documents", "description": "Delete one or more Firestore documents by relative path." },
"get_rules": { "kind": "firestore-get-rules", "description": "Get the active Firestore security rules for the database." },
"validate_rules": { "kind": "firestore-validate-rules", "description": "Validate a Firestore security rules source." }
},
"toolsets": {
"read": ["list_collections", "get_documents", "query_collection"],
"write": ["add_documents", "update_document", "delete_documents"],
"rules": ["get_rules", "validate_rules"]
}
}
To enable only some of them, use the per-category configs below.
Available tools
Every tool takes its inputs from the caller, so a tool definition needs only a kind and a description. Pick a category, then expand Copy as JSON to grab a ready-to-paste config.
- Read
- Write
- Security rules
| Kind | Returns |
|---|---|
firestore-list-collections | Root collections, or the subcollections of a document path |
firestore-get-documents | One or more documents by relative path (e.g., customers/abc123) |
firestore-query-collection | Documents in a collection matching filters, with optional ordering and limit |
Copy as JSON
{
"tools": {
"list_collections": { "kind": "firestore-list-collections", "description": "List Firestore collections." },
"get_documents": { "kind": "firestore-get-documents", "description": "Get documents by path." },
"query_collection": { "kind": "firestore-query-collection", "description": "Query documents in a collection." }
},
"toolsets": { "read": ["list_collections", "get_documents", "query_collection"] }
}
| Kind | Does |
|---|---|
firestore-add-documents | Adds a document with an auto-generated ID |
firestore-update-document | Updates fields of a document, optionally limited to an update mask |
firestore-delete-documents | Deletes one or more documents by path |
Write tools take document data in Firestore's typed JSON format (e.g., {"name": {"stringValue": "Ada"}}), and the tool descriptions explain the format to the AI client.
Copy as JSON
{
"tools": {
"add_documents": { "kind": "firestore-add-documents", "description": "Add a document to a collection." },
"update_document": { "kind": "firestore-update-document", "description": "Update fields of a document." },
"delete_documents": { "kind": "firestore-delete-documents", "description": "Delete documents by path." }
},
"toolsets": { "write": ["add_documents", "update_document", "delete_documents"] }
}
| Kind | Returns |
|---|---|
firestore-get-rules | The active Firestore security rules for the database |
firestore-validate-rules | Validation results for a rules source passed by the caller |
These need the Firebase Rules Viewer role and the Firebase Rules API.
Copy as JSON
{
"tools": {
"get_rules": { "kind": "firestore-get-rules", "description": "Get the active security rules." },
"validate_rules": { "kind": "firestore-validate-rules", "description": "Validate a security rules source." }
},
"toolsets": { "rules": ["get_rules", "validate_rules"] }
}
Add Firestore Toolbox to Mintive
- In Mintive, go to MCP store > Manage store.
- Find Firestore Toolbox in the Catalog tab and click to install it.
- In the setup dialog, enter:
- Project ID (
FIRESTORE_PROJECT): the Google Cloud project that owns the database, shown in the console's top bar. - Database ID (
FIRESTORE_DATABASE): keep the pre-filled(default), the ID Firestore gives a project's first database, unless you created a named database. - Service Account JSON (
FIRESTORE_CREDENTIALS_JSON): the full contents of the key file you downloaded, pasted as is. - Tool Definitions (
TOOLBOX_TOOLS): pre-filled with read-only tools. Keep them, or replace them with a config from Define the tools.
- Project ID (
- Click Save.
If the key or the tool definitions are invalid, the connector fails to start and its logs say why.
Security considerations
- Every user acts as the single configured service account, so grant it Cloud Datastore Viewer unless you intend to allow writes.
- Firestore security rules don't restrict the connector, because they apply only to web and mobile SDK clients. IAM roles on the service account are the real guardrail.
- Omit the write tools from
TOOLBOX_TOOLSto keep a read-only surface even if the service account can write. - The key is stored as a Mintive secret. Rotate it by creating a new key, updating
FIRESTORE_CREDENTIALS_JSON, and deleting the old key in Google Cloud. - Firestore is reached over Google's public API, so the connector has no egress IP to allowlist and doesn't use Private Networks.
Next steps
- Tool customization: Control which tools are exposed to users
- MCP gateway administration: Manage access and permissions