Firestore

You set up a Firestore MCP Server to perform create, read, update, delete, and query operations on Google Firestore collections directly from Claude Desktop. This MCP server exposes a clean set of actions you can invoke to manage Firestore documents and collections without writing boilerplate code.

How to use

You use an MCP client to interact with the Firestore MCP Server by invoking its built‑in tools. The available actions let you create new documents, read existing ones, update fields, delete documents, run queries with filters and ordering, and list all accessible collections. Use these capabilities to build user flows such as managing user profiles, product catalogs, or any structured data stored in Firestore.

How to install

Prerequisites you need before starting are Node.js and npm. Ensure you have a supported Node.js version installed on your machine.

Step 1: Install dependencies

npm install

Step 2: Build the project

npm run build

Step 3: Configure Claude Desktop to load the MCP server

"firestore-mcp": {
  "command": "node",
  "args": [
    "/path/to/firestore-mcp/build/index.js"
  ],
  "env": {
    "GOOGLE_CLOUD_PROJECTS": "project-id"
  }
}

Replace the path in args with the actual path to index.js. Define a comma-separated list of project ids in GOOGLE_CLOUD_PROJECTS. Example: google-project-id1,google-project-id2. The first listed project is the default. The application expects to find .json credential file(s) in the keys folder for each project, e.g. keys/google-project-id1.json, keys/google-project-id2.json. Ensure the cloud service account has appropriate permissions to interact with Cloud Firestore, such as Cloud Datastore Owner or equivalent permissions.

## Additional setup notes

Environment and credentials are needed for Firestore access. Place your service account credentials in the keys folder, one JSON file per project. The underlying server uses the credentials to authenticate API calls to Firestore.

The default project is the first in the comma‑separated list you provide in GOOGLE\_CLOUD\_PROJECTS. You can switch between projects by changing this list, but the first entry remains the default unless you explicitly select a different project in your client flow.

## Troubleshooting and notes

If you encounter credential or permission errors, verify that the service account has sufficient Firestore permissions and that the correct credentials JSON files are present in the keys folder for each listed project.

If the MCP server fails to start, double‑check the build output path in the configuration and confirm that node can locate build/index.js at the specified path.

## Tools and capabilities

The Firestore MCP Server exposes a set of actions that you can call from the MCP client to manage data in Firestore.

## Security considerations

Limit access to the Claude Desktop configuration and the credentials in the keys folder. Use IAM roles and least privilege principles for the service accounts used by each Firestore project.

## Available tools

### getDocument

Fetch a Firestore document by its ID from a specified collection.

### createDocument

Create a new document with provided field data in a collection.

### updateDocument

Update fields of an existing document identified by its ID in a collection.

### deleteDocument

Remove a document by its ID from a collection.

### queryDocuments

Query documents with filters, ordering, and limits to return matching results.

### listCollections

List all available Firestore collections accessible to the configured projects.