What can you do with the Firestore integration?

LiveContext exposes 22 operations on Firestore, covering batch get document, batch write, begin transaction and commit. Common uses include list databases in a project, execute commit programmatically and execute run query programmatically.

Which OAuth scopes does Firestore require?

The operations that declare a scope all need https://www.googleapis.com/auth/datastore.

LiveContext

All integrations

Firestore integration

Google Cloud Firestore NoSQL document database REST API. Create, read, update, and delete documents, run structured queries, manage collections, and handle real-time data with strong consistency and ACID transactions.

22 toolsOAuthAPI docs

Connect Firestore How integrations work

Common Firestore use cases

list databases in a project
execute commit programmatically
execute run query programmatically
execute list index programmatically
execute batch write programmatically
execute create index programmatically
execute get database programmatically
execute get document programmatically
execute list document programmatically
execute create database programmatically

What you can do with Firestore

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Batch get document, 1 operation

POSTbatch_get_documents
Gets multiple documents in a single request. Returns results in an unspecified order.

Batch write, 1 operation

POSTbatch_write
Applies multiple writes atomically, without transaction guarantees. Writes are applied in order.

Begin transaction, 1 operation

POSTbegin_transaction
Starts a new transaction and returns a transaction ID to use in subsequent read/write operations.

Commit, 1 operation

POSTcommit
Commits a transaction, applying all writes within the transaction atomically.

Create database, 1 operation

POSTcreate_database
Creates a new Firestore database in the specified project.

Create document, 1 operation

POSTcreate_document
Creates a new document in the specified collection.

Create index, 1 operation

POSTcreate_index
Creates a composite index for a collection group. Returns a long-running operation.

Database, 1 operation

GETlist_databases
Lists all databases in a Google Cloud project.

Delete database, 1 operation

DELETEdelete_database
Deletes a Firestore database and all its documents.

Delete document, 1 operation

DELETEdelete_document
Deletes a document from Firestore.

Export document, 1 operation

POSTexport_documents
Exports a copy of all or a subset of documents from Firestore to Cloud Storage.

Get database, 1 operation

GETget_database
Gets information about a Firestore database.

Get document, 1 operation

GETget_document
Gets a single document from Firestore by its full path.

Import document, 1 operation

POSTimport_documents
Imports documents into Firestore from a Cloud Storage export.

List collection id, 1 operation

POSTlist_collection_ids
Lists all the collection IDs underneath a document.

List document, 1 operation

GETlist_documents
Lists documents in a collection.

List index, 1 operation

GETlist_indexes
Lists the composite indexes defined for a collection group.

Rollback transaction, 1 operation

POSTrollback_transaction
Rolls back a transaction, discarding all pending writes.

Run aggregation query, 1 operation

POSTrun_aggregation_query
Runs an aggregation query (e.g. COUNT) over a collection or collection group.

Run query, 1 operation

POSTrun_query
Runs a structured query against Firestore documents.

Update database, 1 operation

PATCHupdate_database
Updates the configuration of an existing Firestore database.

Update document, 1 operation

PATCHupdate_document
Updates or inserts a document. A patch operation; only provided fields are updated.

OAuth scopes Firestore requires

Each operation declares the scopes Firestore requires for it.

https://www.googleapis.com/auth/datastoreneeded by batch_get_documents, batch_write, begin_transaction and 19 more

Use Firestore from Claude Code, Cursor or Codex

Connect Firestore in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Firestore operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Firestore

Create your workspace
Sign up free. Nothing to install.
Connect Firestore once
Add your Firestore connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.

Firestore integration FAQ

What can you do with the Firestore integration?: LiveContext exposes 22 operations on Firestore, covering batch get document, batch write, begin transaction and commit. Common uses include list databases in a project, execute commit programmatically and execute run query programmatically.
Which OAuth scopes does Firestore require?: The operations that declare a scope all need https://www.googleapis.com/auth/datastore.