Firestore MCP Server

other

Firestore is often where the actual state of an application lives, and poking at it usually means opening the console or writing a one-off script. This connection lets Neotask's agent query, read, and write documents in a Google Cloud Firestore database directly, manage collections, and run transactions against the data your app depends on.

• Reads and writes Firestore documents directly, not through a console UI
• Manages collections as part of the same conversation
• Runs transactions against live application data when the task calls for it

What you can automate

Firestore MCP Server

Query, read, and write documents in a Google Cloud Firestore database. Manage collections and run transactions against Firestore-backed application data.

Real workflows

Investigate and fix a bad document without leaving chat

You describe a record that looks wrong in production. Neotask queries the relevant Firestore collection, shows you the document, and — once you confirm — writes the correction as a transaction.

Frequently asked questions

Can it modify collection structure, or only documents?

It manages collections and documents, and can run transactions against the data, not just read individual records.

Is this safe to point at a production database?

It operates directly on whichever Firestore database it's connected to, so treat write operations with the same care you would a manual console edit.