FireCMS Cloud MCP Server: Manage Firestore Data and Schemas from Your Assistant

• Lists your FireCMS Cloud projects

  Shows every FireCMS Cloud project your account can reach. The service account for each project is stripped from the output. Other tools take a project ID from this list.

  Try: “Which FireCMS projects do I have?”

  Network · list_projects

• Reads documents from a collection

  Fetches documents from a Firestore collection, with optional filters, ordering and a limit.

  Try: “Show the 20 newest orders from the orders collection.”

  Network · list_documents

• Opens one document

  Returns every field of a single Firestore document, given its collection path and ID.

  Try: “Open the document products/abc123.”

  Network · get_document

• Counts documents in a collection

  Returns how many documents a Firestore collection holds, without loading them.

  Try: “How many users are in the users collection?”

  Network · count_documents

• Lists top-level Firestore collections

  Reads the live list of root collections in the project, including ones created moments ago. These are the paths that can become CMS collections.

  Try: “Which collections exist in my Firestore?”

  Network · get_root_collections

• Lists collections nested under a document

  Returns the subcollections of one document with their full paths, so nested data can be found and turned into CMS collections.

  Try: “What subcollections does the document users/u1 have?”

  Network · list_subcollections

• Lists Firestore databases

  Lists the Firestore databases in a project. You only need it when the project uses more than the default database.

  Try: “Does this project have more than one Firestore database?”

  Network · list_databases

• Drafts a schema from real data

  Samples documents from a Firestore path and works out field types, enum candidates and validation from them. Nothing is saved, so you can edit the draft first.

  Try: “Preview a schema for the products collection without saving it.”

  Network · preview_inferred_schema

• Lists saved collection schemas

  Returns every collection configuration saved for the project, with names, paths and properties.

  Try: “List all collection schemas in my FireCMS project.”

  Network · list_collection_schemas

• Shows one collection schema

  Returns the full definition of one collection: properties, validation rules, display settings and subcollections.

  Try: “Show the schema for the blog collection.”

  Network · get_collection_schema

• Exports a collection as JSON

  Returns documents from a collection as JSON, useful for backups, analysis or migration. Use the limit for large collections.

  Try: “Export the first 100 documents of the customers collection.”

  Network · export_collection

• Lists project users and roles

  Shows everyone with access to a project and whether each is an admin, editor or viewer.

  Try: “Who has admin access to this project?”

  Network · list_users

• Shows project settings

  Returns the project name, logo and brand colors, plan and trial status, feature toggles such as text search and history, and the default locale.

  Try: “What plan and settings does my project use?”

  Network · get_project_config

• Shows who you are signed in as

  Returns the FireCMS user the server is acting for.

  Try: “Which FireCMS account am I using?”

  Network · firecms_get_current_user

• Drafts a schema from a description

  Asks the FireCMS backend to write a complete collection schema from a plain-language description. It returns the draft and does not save it.

  Try: “Generate a collection for a blog with posts, authors and tags.”

  Network · generate_collection

• Proposes edits to a schema

  Asks the FireCMS backend to change an existing schema from a plain-language request, such as adding a field. It returns the updated schema and the operations it performed, and does not save it.

  Try: “Make the title field required with a 100 character limit.”

  Network · modify_collection

• Adds a document

  Creates a new Firestore document in a collection from a set of field values you provide.

  Try: “Add a product named Mug with price 12 to the products collection.”

  Write · create_document

• Changes fields on a document

  Updates only the fields you name on an existing document and merges them with what is there.

  Try: “Set status to published on posts/abc123.”

  Write · update_document

• Deletes a document

  Removes a Firestore document. The tool description says the action is permanent.

  Try: “Delete the document orders/o-1001.”

  Delete · delete_document

• Bulk-loads documents (max 500)

  Writes up to 500 documents per call into a collection for seeding, migration or restoring a backup. A document with an existing ID is overwritten unless merge is on.

  Try: “Import these 40 products into the products collection.”

  Delete · import_documents

• Creates or replaces a collection schema

  Saves a collection definition in FireCMS, replacing one with the same ID. It needs at least an ID, path and name, and the underlying data is unchanged.

  Try: “Create a Products collection with name, price and status fields.”

  Write · save_collection_schema

• Edits parts of a collection schema

  Changes only the top-level fields you give, such as name, group, display settings or properties, and keeps the rest.

  Try: “Rename the Posts collection to Articles.”

  Write · update_collection_schema

• Adds or edits one field in a schema

  Adds a field to a collection schema or updates an existing one, leaving other fields alone. New fields go at the end of the display order.

  Try: “Add a required email field to the customers collection.”

  Write · save_property

• Removes a field from a schema

  Removes a field definition from the CMS configuration. The field stays in existing Firestore documents.

  Try: “Remove the legacy_id field from the products schema.”

  Delete · delete_property

• Removes a collection from the CMS

  Deletes the collection configuration so it no longer shows in FireCMS. The Firestore data is not deleted.

  Try: “Remove the drafts collection from the CMS.”

  Delete · delete_collection_schema

• Builds and saves collections from data

  Samples documents at the paths you choose, infers field types, and has an LLM pick display names, icons, groups and widgets. It saves the result and skips paths that are already mapped or empty. Needs admin.

  Try: “Turn the orders and customers paths into CMS collections.”

  Write · infer_collections_from_data

• Sets up every unmapped collection

  Finds each root Firestore collection that has no CMS collection, infers a schema for each and saves them all. Existing collections are left alone, so it is safe to re-run. Needs admin.

  Try: “Set up FireCMS collections for everything in my database.”

  Write · setup_all_collections

• Invites a user

  Invites someone to a project by email with the roles you pick. An existing user with that email gets their roles replaced. Admin only.

  Try: “Invite sam@example.com to the project as an editor.”

  Write · add_user

• Changes a user's roles

  Sets new roles for a user who already has access to the project. Admin only.

  Try: “Make jo@example.com a viewer.”

  Write · update_user_roles

• Removes a user

  Takes a user's access to the project away. Admin only.

  Try: “Remove lee@example.com from the project.”

  Delete · remove_user

• Renames the project

  Changes the display name of a FireCMS project.

  Try: “Rename the project to Acme Admin.”

  Write · update_project_name

• Changes brand colors

  Sets the primary and secondary colors of the CMS interface from hex values.

  Try: “Set the primary color to #0070F4.”

  Write · update_project_colors

• Changes the default locale

  Sets the CMS default locale, which affects things like date formatting.

  Try: “Change the default locale to de.”

  Write · update_default_locale

• Turns text search on or off

  Enables or disables local text search for the project.

  Try: “Turn on text search for my project.”

  Write · toggle_text_search

• Turns change history on or off

  Enables or disables the audit log of document changes for the project.

  Try: “Turn on entity history for the project.”

  Write · toggle_entity_history

• Adds the FireCMS access rule

  Adds a Firestore and Storage rule that lets users with the FireCMS claim read and write. Without it the CMS shows "Missing Firestore Security Rules". Needs admin.

  Try: “Apply the FireCMS security rules to my project.”

  Write · apply_firestore_security_rules

• Repairs the project web app

  Creates the FireCMS web app inside your Firebase project, or reuses the existing one. Use it when that step failed during connect. Needs admin.

  Try: “Retry creating the FireCMS web app for my project.”

  Write · create_firecms_webapp

• Connects a Firebase project

  On the local server, creates a delegated service account in your project, makes you admin, creates the FireCMS project on the free plan and by default adds the access rule to your security rules. It fails if the project is already connected. On the hosted server it only returns a link to connect in the web app.

  Try: “Connect my Firebase project acme-prod to FireCMS.”

  Write · connect_project_to_firecms

• Signs in with Google (local only)

  Opens a browser for Google sign-in. The local server needs this before its other tools work, and it saves the tokens in a file in your home folder.

  Try: “Sign me in to FireCMS.”

  Write · firecms_login

• Signs out (local only)

  Signs out of FireCMS Cloud and revokes the current session.

  Try: “Sign me out of FireCMS.”

  Write · firecms_logout

• Lists Google Cloud projects (local only)

  Lists the Google Cloud and Firebase projects your Google account can reach, with flags for what each still needs before it can be connected.

  Try: “Which of my Firebase projects can I connect to FireCMS?”

  Network · list_firebase_projects

• Checks one project's readiness (local only)

  Reports whether Firebase, Firestore, Storage, Auth and the required APIs are on for one Google Cloud project, and so what is missing.

  Try: “What is missing on acme-prod before I can connect it?”

  Network · get_project_setup_status

• Lists Firestore locations (local only)

  Lists the locations where a new Firestore database can be created, such as eur3 or us-central.

  Try: “Where can I create a Firestore database?”

  Network · list_firestore_locations

• Turns on required Google APIs (local only)

  Enables the Google Cloud APIs FireCMS needs on a project. Running it again is safe.

  Try: “Enable the APIs FireCMS needs on acme-prod.”

  Write · enable_project_apis

• Creates the Firestore database (local only)

  Creates the default Firestore database in a Google Cloud project at the location you choose. The location is permanent.

  Try: “Create a Firestore database in eur3 for acme-prod.”

  Write · enable_firestore

Watch out for

• It can delete documents permanently

  The delete document tool removes a Firestore document and its description calls the action permanent. Back up with the export tool first and approve each delete. github.com

• Bulk import overwrites existing documents

  Import writes up to 500 documents per call and replaces any document with the same ID unless merge is on. Ask the assistant to show the IDs before it runs. github.com

• It can remove users and change roles

  The add, update-role and remove user tools change who can reach the project. Only admins can use them, so keep the admin role to people you trust. github.com

• Schema tools can overwrite or remove collections

  Saving a schema replaces one with the same ID, and the delete tools remove collection or field settings from the CMS. The Firestore data itself is not deleted by these tools. github.com

• Local connect edits Google Cloud and security rules

  On the local server, connecting a project creates a service account and adds an access rule to Firestore and Storage rules. The local server uses a Google token with cloud-platform scope, so use an account that only reaches the projects you intend. github.com

• Schema inference sends sample data to an LLM

  The bulk collection setup samples your documents and the FireCMS backend uses an LLM to pick names, icons and widgets. Skip it for collections with sensitive content. github.com

Security advisories