Connectors · Files & documents

Google Cloud Firestore MCP server for AI agents.

actionlake is an MCP gateway: one remote MCP server that connects Claude and other MCP clients to Google Cloud Firestore and the rest of your systems. It gives your agent 63 Google Cloud Firestore actions (31 reads, 20 writes and 12 that wait for a confirmation) and holds the Google Cloud Firestore credential itself, so the agent never does. It paces Google Cloud Firestore's limits and records every call. Connecting Google Cloud Firestore needs your own Google Cloud Firestore OAuth app and one admin sign-in.

Connect Google Cloud Firestore free See pricing

100,000 free calls a month. No card, no email, no password: press Start a free sandbox on the next screen and keep the key it shows you.

claude mcp add --transport http actionlake https://connect.actionlake.com/mcp

63actionsin one signed file
31readlook, never change
20writecreate and update
12wait for a yesdestructive, confirmed first

Set up

Connect Google Cloud Firestore in three steps.

01
Add actionlake to Claude.
Run the command once in Claude Code; its consent page can create a free sandbox: 100,000 calls a month, no card. In the Claude app, add a custom connector with the URL below and paste your key on the consent page. Creating a new sandbox from the Claude app is not yet tested by us.
https://connect.actionlake.com/mcp
02
Connect Google Cloud Firestore.
OAuth 2.0, authorization code with PKCE. You register your own OAuth app with Google Cloud Firestore, an admin signs in once, and you paste the app's client id and secret and the tokens from that sign-in; actionlake renews the access token from then on. actionlake stores what you paste write-only, sealed under your tenant's key.
Before the first sign-in, Google Cloud Firestore needs an OAuth app of your own, registered in its developer portal. actionlake has no Google Cloud Firestore app to lend you.
- access_tokenAccess token from one sign-in with your own OAuth app
- refresh_tokenRefresh token from the same sign-in; the access token is renewed from it
- client_idGoogle OAuth client id (Google Cloud console > APIs & Services > Credentials; enable the Cloud Firestore API on the…
- client_secretGoogle OAuth client secret
```
account { op: "connections.requirements", service: "gcp_firestore" }
# free: exactly what to paste, and what is found for you
```

Make the first call. Check before a write.

Ask in plain words; Claude picks the action. Before anything changes, check validates the call and prices it, for free.

do    { action: "gcp_firestore.locations.get" }# locations: get · read · 1 upstream callcheck { action: "gcp_firestore.databases.create", input: { … } }# free: inputs, permissions, cost and confirmations, nothing sent

Google Cloud Firestore at a glance

Sign-in: OAuth 2.0, authorization code with PKCE. You register your own OAuth app with Google Cloud Firestore, an admin signs in once, and you paste the app's client id and secret and the tokens from that sign-in; actionlake renews the access token from then on.
You provide: access_tokenrefresh_tokenclient_idclient_secret
Limits we pace to: 600 calls a minute, per connection
API covered: Google Cloud Firestore API v1 (documents, queries, transactions, databases, indexes, fields, backups, operations) API firestore v1 (Discovery revision 20261013)firestore.googleapis.com
Built from: Google Cloud Firestore's documentation, read 23 October 2026firestore.googleapis.com cloud.google.com
Service file: Version 1.0.0, signed (Ed25519)
Cached reads: 19 of 31 reads, for up to 5 minutes; a write clears what it affects
Shared entities: 1, so ask can line Google Cloud Firestore up with your other systems
Data: Processed and stored in Sydney, Australia. No US region yet

Capabilities

What an AI agent can do in Google Cloud Firestore.

63 actions in 10 areas. Every one carries its effect, so a key can allow the reads and hold the rest.

31readlook, never change
20writecreate and update
12destructivewait for a confirmation

Documents
21
13 read · 7 write · 1 destructive
Documents: batch get · Documents: begin transaction · Documents: create document (database root) · Documents: create document (under a document)
Databases
10
2 read · 6 write · 2 destructive
Databases: list · Databases: create · Databases: get · Databases: patch
User creds
7
2 read · 2 write · 3 destructive
User creds: create · User creds: list · User creds: get · User creds: delete
Backup schedules
5
2 read · 2 write · 1 destructive
Backup schedules: create · Backup schedules: list · Backup schedules: get · Backup schedules: delete
Change streams
4
2 read · 1 write · 1 destructive
Change streams: create · Change streams: list · Change streams: get · Change streams: delete
Collection groups indexes
4
2 read · 1 write · 1 destructive
Collection groups indexes: create · Collection groups indexes: list · Collection groups indexes: get · Collection groups indexes: delete
Operations
4
2 read · 0 write · 2 destructive
Operations: list · Operations: get · Operations: delete · Operations: cancel
Backups
3
2 read · 0 write · 1 destructive
Backups: list · Backups: get · Backups: delete

2 more areas · 5 actions

Collection groups fields 3
Locations 2

Top actions

The Google Cloud Firestore API, shaped for agents.

The ids your agent types, what each does, and the one name it shares with other systems. 9 of Google Cloud Firestore's 9 action names are shared with at least one other connector, so an agent learns them once.

Action	What it does	Effect	Same name in
`gcp_firestore.databases.list`Databases: list	List all the databases in the project.	read	`infra.database.list`7 connectors
`gcp_firestore.databases.create`Databases: create	Create a database.	write	`infra.database.create`6 connectors
`gcp_firestore.databases.delete`Databases: delete	Deletes a database.	destructive	`infra.database.delete`7 connectors
`gcp_firestore.user_creds.list`User creds: list	List all user creds in the database.	read	`infra.database_user.list`7 connectors
`gcp_firestore.user_creds.create`User creds: create	Create a user creds.	write	`infra.database_user.create`7 connectors
`gcp_firestore.documents.list`Documents: list (under a document)	Lists documents.	read	this connector
`gcp_firestore.databases.clone`Databases: clone	Creates a new database by cloning an existing one.	write	this connector
`gcp_firestore.operations.list`Operations: list	Lists operations that match the specified filter in the request.	read	this connector
`gcp_firestore.databases.restore`Databases: restore	Creates a new database by restoring from an existing backup.	write	this connector
`gcp_firestore.documents.batch_get`Documents: batch get	Gets multiple documents.	read	this connector
`gcp_firestore.collection_groups_indexes.list`Collection groups indexes: list	Lists composite indexes.	read	this connector
`gcp_firestore.collection_groups_indexes.create`Collection groups indexes: create	Creates a composite index.	write	this connector

Try it

Prompts to paste into Claude.

Each one names the Google Cloud Firestore actions it will call, so you know what it reads and what it changes before you send it.

Readread
Locations: get in Google Cloud Firestore and tell me what stands out.
callsgcp_firestore.locations.get
Writewrite
Databases: create in Google Cloud Firestore. Show me exactly what you will send before you save it.
callsgcp_firestore.databases.create

Governance for Google Cloud Firestore

Destructive actions wait for a yes.

12 Google Cloud Firestore actions are destructive. These are all of them:

Databases: deletegcp_firestore.databases.delete
User creds: deletegcp_firestore.user_creds.delete
Documents: deletegcp_firestore.documents.delete
Operations: deletegcp_firestore.operations.delete
Databases: bulk delete documentsgcp_firestore.databases.bulk_delete_documents
Operations: cancelgcp_firestore.operations.cancel
Collection groups indexes: deletegcp_firestore.collection_groups_indexes.delete
Backups: deletegcp_firestore.backups.delete
User creds: disablegcp_firestore.user_creds.disable
Change streams: deletegcp_firestore.change_streams.delete
Backup schedules: deletegcp_firestore.backup_schedules.delete
User creds: reset passwordgcp_firestore.user_creds.reset_password

A destructive action runs only with confirm: true. Under the human policy the agent cannot confirm for itself: the run stops until a named person approves, in the console or from a signed link in an email. The cap on a key is refused before the call is sent, never after.

dogcp_firestore.databases.deleteconfirm_policy: human

Databases: delete?

intent: the user asked me to databases: delete

run suspended · waiting for a named person · key gcp-firestore-agent cannot confirm itself

In the console, or from an emailed signed link.

a key for this connector

account {  op: "keys.create", name: "gcp-firestore-agent",  allowed_actions: ["gcp_firestore.*"], cap_calls: 2000,  confirm_policy: "human_for_writes",  approval_rules: [    { match: "gcp_firestore.databases.delete", approver: "[email protected]" },    { match: "gcp_firestore.user_creds.delete", approver: "[email protected]" },    { match: "gcp_firestore.documents.delete", approver: "[email protected]" }  ]}

Illustrative. Scoped to Google Cloud Firestore only, capped at 2,000 upstream calls, every write confirmed, and the destructive ones approved by a named person.

Cost

What Google Cloud Firestore costs on actionlake.

Every Google Cloud Firestore action is one upstream call, the only thing actionlake bills. Searching, check, cost, account and any call Google Cloud Firestore refused with 401, 403, 429 or a 5xx are free. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000.

1upstream call per actionall 63 Google Cloud Firestore actions
10actions pageeach page of a long list is one call
19reads can be cacheda cache hit costs nothing
100,000calls a month, freepaid plans from US$49 a month for 250,000

See pricing

Action index

Every Google Cloud Firestore action.

63 actions by area: the id your agent calls, what it does, and its effect.

Documents21

gcp_firestore.documents.batch_getDocuments: batch getread
gcp_firestore.documents.batch_writeDocuments: batch writewrite
gcp_firestore.documents.begin_transactionDocuments: begin transactionwrite
gcp_firestore.documents.commitDocuments: commitwrite
gcp_firestore.documents.create_documentDocuments: create document (database root)write
gcp_firestore.documents.create_document_nestedDocuments: create document (under a document)write
gcp_firestore.documents.deleteDocuments: deletedestructive
gcp_firestore.documents.execute_pipelineDocuments: execute pipelineread
gcp_firestore.documents.getDocuments: getread
gcp_firestore.documents.listDocuments: list (under a document)read
gcp_firestore.documents.list_collection_idsDocuments: list collection ids (database root)read
gcp_firestore.documents.list_collection_ids_nestedDocuments: list collection ids (under a document)read
gcp_firestore.documents.list_documentsDocuments: list documents (database root)read
gcp_firestore.documents.partition_queryDocuments: partition query (database root)read
gcp_firestore.documents.partition_query_nestedDocuments: partition query (under a document)read
gcp_firestore.documents.patchDocuments: patchwrite
gcp_firestore.documents.rollbackDocuments: rollbackwrite
gcp_firestore.documents.run_aggregation_queryDocuments: run aggregation query (database root)read
gcp_firestore.documents.run_aggregation_query_nestedDocuments: run aggregation query (under a document)read
gcp_firestore.documents.run_queryDocuments: run query (database root)read
gcp_firestore.documents.run_query_nestedDocuments: run query (under a document)read

Databases10

gcp_firestore.databases.bulk_delete_documentsDatabases: bulk delete documentsdestructive
gcp_firestore.databases.cloneDatabases: clonewrite
gcp_firestore.databases.createDatabases: createwrite
gcp_firestore.databases.deleteDatabases: deletedestructive
gcp_firestore.databases.export_documentsDatabases: export documentswrite
gcp_firestore.databases.getDatabases: getread
gcp_firestore.databases.import_documentsDatabases: import documentswrite
gcp_firestore.databases.listDatabases: listread
gcp_firestore.databases.patchDatabases: patchwrite
gcp_firestore.databases.restoreDatabases: restorewrite

User creds7

gcp_firestore.user_creds.createUser creds: createwrite
gcp_firestore.user_creds.deleteUser creds: deletedestructive
gcp_firestore.user_creds.disableUser creds: disabledestructive
gcp_firestore.user_creds.enableUser creds: enablewrite
gcp_firestore.user_creds.getUser creds: getread
gcp_firestore.user_creds.listUser creds: listread
gcp_firestore.user_creds.reset_passwordUser creds: reset passworddestructive

Backup schedules5

gcp_firestore.backup_schedules.createBackup schedules: createwrite
gcp_firestore.backup_schedules.deleteBackup schedules: deletedestructive
gcp_firestore.backup_schedules.getBackup schedules: getread
gcp_firestore.backup_schedules.listBackup schedules: listread
gcp_firestore.backup_schedules.patchBackup schedules: patchwrite

Change streams4

gcp_firestore.change_streams.createChange streams: createwrite
gcp_firestore.change_streams.deleteChange streams: deletedestructive
gcp_firestore.change_streams.getChange streams: getread
gcp_firestore.change_streams.listChange streams: listread

Collection groups indexes4

gcp_firestore.collection_groups_indexes.createCollection groups indexes: createwrite
gcp_firestore.collection_groups_indexes.deleteCollection groups indexes: deletedestructive
gcp_firestore.collection_groups_indexes.getCollection groups indexes: getread
gcp_firestore.collection_groups_indexes.listCollection groups indexes: listread

Operations4

gcp_firestore.operations.cancelOperations: canceldestructive
gcp_firestore.operations.deleteOperations: deletedestructive
gcp_firestore.operations.getOperations: getread
gcp_firestore.operations.listOperations: listread

Backups3

gcp_firestore.backups.deleteBackups: deletedestructive
gcp_firestore.backups.getBackups: getread
gcp_firestore.backups.listBackups: listread

Collection groups fields3

gcp_firestore.collection_groups_fields.getCollection groups fields: getread
gcp_firestore.collection_groups_fields.listCollection groups fields: listread
gcp_firestore.collection_groups_fields.patchCollection groups fields: patchwrite

Locations2

gcp_firestore.locations.getLocations: getread
gcp_firestore.locations.listLocations: listread

Questions

The Google Cloud Firestore MCP server, answered.

Is there a Google Cloud Firestore MCP server for Claude?

Yes. actionlake is an MCP gateway: a remote MCP server that gives Claude, or another MCP client, 63 Google Cloud Firestore actions across documents, databases, user creds and backup schedules, through the same eight tools it uses for every other connector. actionlake is independent; it is not made or endorsed by Google Cloud Firestore.

What do I need to connect Google Cloud Firestore?

Your own Google Cloud Firestore OAuth app, registered with Google Cloud Firestore (its client id and client secret), and the access and refresh tokens from one admin sign-in. actionlake has no Google Cloud Firestore app of its own, so this is not a one-step consent. actionlake renews the access token as it expires. The free call account { op: "connections.requirements", service: "gcp_firestore" } lists exactly what to paste.

Can an AI agent delete or change things in Google Cloud Firestore?

Only if its key allows it, and only with an explicit confirmation. 12 Google Cloud Firestore actions are destructive, including databases: delete, user creds: delete and documents: delete. Each runs only with confirm: true. Under the human confirm policy, or an approval rule on the key, the run waits until a named person approves it.

Will an AI agent use up my Google Cloud Firestore API limit?

actionlake paces every call to the limits in the Google Cloud Firestore service file: 600 calls a minute per connection. Repeated reads are answered from cache (19 Google Cloud Firestore actions can be), which never reaches Google Cloud Firestore.

What does a Google Cloud Firestore action cost?

One upstream call, the only unit actionlake bills. A list that pages bills one call per page (10 Google Cloud Firestore actions page). Cache hits, searches, dry runs and calls Google Cloud Firestore refused with 401, 403, 429 or a 5xx are free. The Free plan includes 100,000 calls a month with no card. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000.

Which Google Cloud Firestore API does it cover?

The Google Cloud Firestore API v1 (documents, queries, transactions, databases, indexes, fields, backups, operations) API firestore v1 (Discovery revision 20261013) at firestore.googleapis.com. It is built from Google Cloud Firestore's documentation as read on 23 October 2026. 63 actions in 10 areas, each one in the signed service file (version 1.0.0).

Does actionlake keep my Google Cloud Firestore data, and where?

actionlake processes and stores data in Sydney, Australia; there is no US region yet. Reads may be cached for up to 5 minutes, and a write clears the reads it affects. Each run's request and response is kept, sealed, for your plan's trace window: 1 day on Free, 3 days on Starter, 7 days on Pro, 14 days on Team, 30 days on Business and 30 days on Enterprise. Your Google Cloud Firestore credential is sealed under your tenant's key, never logged and never returned. Your traffic is not used to train models.

Which AI clients can use it?

Claude Code, tested by us end to end, and the Claude app as a custom connector, tested by us with an existing key. Other MCP clients that support remote servers over Streamable HTTP (MCP revisions 2025-06-18 and 2025-11-25) and OAuth dynamic client registration, or a bearer header, should connect the same way; we have not tested them. Or plain REST, under the same action names.

Give your agent Google Cloud Firestore today.

Connect Google Cloud Firestore free See pricing

Start free - 100,000 calls/month, no card. No signup. Hard caps on every key. Cached answers are free.

Google Cloud Firestore MCP server for AI agents.

Connect Google Cloud Firestore in three steps.

Add actionlake to Claude.

Connect Google Cloud Firestore.

Make the first call. Check before a write.

What an AI agent can do in Google Cloud Firestore.

Documents

Databases

User creds

Backup schedules

Change streams

Collection groups indexes

Operations

Backups