All servers / CMS / FireCMS MCP server
FireCMS MCP server
MCP server for FireCMS Cloud — manage projects, collections, users, and AI features via the Model Context Protocol
Tested by ConnectATDScore 86 out of 100. Tested 2026-11-19 on package version 3.5.3. Package: @firecms/mcp-server · source
Score breakdown
| Runs | 18 / 20 | |
|---|---|---|
| Tool descriptions | 20 / 20 | |
| Package safety | 20 / 20 | |
| Maintenance | 20 / 20 | |
| Adoption | 8 / 20 |
What we saw
- Starts and answers the MCP handshake: yes (9.6 seconds including download)
- Tools offered: 45
- Last published: 2026-11-15
- Weekly downloads (npm): 607
- License: MIT · Direct dependencies: 5
Want this server set up for your team?
ConnectATD builds AI automation and wires up MCP servers like this one. Tell us what you are trying to do.
Talk to ConnectATDTools and how they are described
Agents choose tools from these descriptions. Under each name you can see how many of its parameters are explained.
firecms_get_current_userno parametersGet the currently authenticated FireCMS user
list_firebase_projectsno parametersList the Google Cloud / Firebase projects the signed-in user can access, and whether each one is ready to be connected to FireCMS Cloud. Each entry reports: - `fireCMSProject`: true if it is already connected to FireCMS Cloud - `cloudProjectConfigurationStatus.firebaseEnabled` / `firestoreEnabled` / `apisEnabled` / `authEnabled`: what connecting requires Connecting needs Firebase, Firestore and Firebase Authentication enabled.
get_project_setup_status1 of 1 parameter describedGet the detailed FireCMS readiness status of a single Google Cloud project: whether Firebase, Firestore, Storage, Auth and the required APIs are enabled, and so what is still missing before it can be connected.
list_firestore_locationsno parametersList the locations available for a new Firestore database, as location IDs such as 'eur3' or 'us-central'.
enable_project_apis1 of 1 parameter describedEnable the Google Cloud APIs that FireCMS requires on a project (reported as `apisEnabled` in its setup status). Safe to run more than once.
enable_firestore2 of 2 parameters describedCreate the default Firestore database in a Google Cloud project, in the given location. The location is permanent and cannot be changed later.
connect_project_to_firecms3 of 3 parameters describedConnect an existing Firebase project to FireCMS Cloud. It creates a delegated service account in the project with the permissions FireCMS needs, registers the signed-in user as an admin, creates the FireCMS project on the free plan, and by default adds FireCMS's access rule to the project's Firestore and Storage security rules. Firebase, Firestore and Firebase Authentication must already be enabled on the project. Authentication cannot be enabled through any API: it is switched on once in the Firebase console. Fails if the project is already connected.
apply_firestore_security_rules1 of 1 parameter describedAdd FireCMS's access rule to a project's Firestore and Storage security rules. Requires admin. FireCMS Cloud reads the customer's Firestore from the browser using the signed-in user's own token, so it needs a rule granting access to users carrying the `fireCMSUser` claim: match /{document=**} { allow read, write: if request.auth.token.fireCMSUser; } Without it the CMS shows "Missing Firestore Security Rules" and no collection opens, although this server keeps working: it reads through the backend's service account, which bypasses security rules. The rule is injected into the existing ruleset rather than replacing it, and a project that already has it is left alone, so it is safe to run again. Connecting a project applies it already; this repairs projects connected earlier, or where that step failed.
create_firecms_webapp1 of 1 parameter describedCreate the FireCMS web app inside the client's Firebase project, or reuse the one already there. Connecting a project normally does this; this repairs a project where that step failed. Requires admin.
list_projectsno parametersList all FireCMS Cloud projects accessible by the authenticated user
get_root_collections2 of 2 parameters describedList all Firestore root-level collections in a FireCMS project — the paths that can be turned into CMS collections. Read live from Firestore, so collections created moments ago are included.
list_subcollections3 of 3 parameters describedList the subcollections of a specific document, with their full paths: nested data that can be turned into CMS collections.
list_users1 of 1 parameter describedList all users that have access to a FireCMS project, including their roles (admin, editor, viewer)
add_user3 of 3 parameters describedInvite a new user to a FireCMS project. Sends an invitation email. Admin-only. If the email already belongs to a user of the project, their roles are replaced by these.
update_user_roles3 of 3 parameters describedUpdate the roles of an existing user in a FireCMS project. Admin-only.
remove_user2 of 2 parameters describedRemove a user from a FireCMS project, revoking their access. Admin-only.
list_databases1 of 1 parameter describedList the Firestore databases of a project. Only needed for projects using more than the '(default)' database — the resulting database IDs can be passed to the other introspection and document tools.
preview_inferred_schema4 of 4 parameters describedRead a sample of real documents from a Firestore path and infer a FireCMS collection schema from them, without saving anything. Works for any path, subcollections included. Inference is structural only: it derives data types, enum candidates and validation from the sampled values. The result is a complete collection schema that can be edited and saved as it is.
infer_collections_from_data2 of 2 parameters describedInfer collections from the existing Firestore data at the given paths, and save them to the project. Requires admin. For each path the backend samples documents, infers the property types, then uses an LLM to pick display names, a singular name, an icon, a navigation group and field widgets. Paths already mapped to a collection, and paths with no documents, are skipped.
setup_all_collections2 of 2 parameters describedDiscover every Firestore root collection in the project that is not yet mapped to a collection, infer a collection schema for each (display names and widgets picked by an LLM), and save them all. Requires admin. Covers every database of the project. Collections that already exist are left alone, so it is safe to run again later to pick up new Firestore collections. Can take a while on large projects.
get_project_config1 of 1 parameter describedGet the full configuration for a FireCMS project, including: - Project name, logo, and brand colors (primary/secondary) - Subscription plan and trial status - Feature toggles (text search, entity history, App Check) - Default locale settings - Customization revision info
update_project_name2 of 2 parameters describedUpdate the display name of a FireCMS project.
update_project_colors3 of 3 parameters describedUpdate the primary and/or secondary brand colors for the CMS UI. Colors should be hex values (e.g., '#0070F4').
update_default_locale2 of 2 parameters describedChange the default locale for the CMS (affects date formatting, etc.).
toggle_text_search2 of 2 parameters describedEnable or disable the local text search feature for a project.
toggle_entity_history2 of 2 parameters describedEnable or disable entity history tracking (audit log of document changes) for a project.
list_collection_schemas1 of 1 parameter describedList all persisted collection schemas for a FireCMS project. Returns the collection configurations (name, path, properties, etc.) that define how data is displayed and edited in the CMS.
get_collection_schema2 of 2 parameters describedGet the full schema definition for a specific collection, including all properties, validation rules, display configuration, and subcollection definitions.
save_collection_schema3 of 3 parameters describedCreate or fully replace a collection schema. This defines how a Firestore collection is displayed and edited in FireCMS. Requires at minimum: id, path, and name. Example schema: { "id": "products", "path": "products", "name": "Products", "singularName": "Product", "icon": "ShoppingCart", "description": "Product catalog", "group": "Shop", "properties": { "name": { "dataType": "string", "name": "Name", "validation": { "required": true } }, "price": { "dataType": "number", "name": "Price", "validation": { "required": true, "min": 0 } }, "status": { "dataType": "string", "name": "Status", "enumValues": [ { "id": "draft", "label": "Draft" }, { "id": "published", "label": "Published" } ]} }, "propertiesOrder": ["name", "price", "status"] }
update_collection_schema3 of 3 parameters describedPartially update an existing collection schema. Only the top-level fields given are changed (merged with the existing schema): for example the name, group, display settings or properties.
delete_collection_schema2 of 2 parameters describedDelete a collection schema from FireCMS. This removes the collection configuration from the CMS — it does NOT delete the underlying Firestore data. The collection will simply no longer appear in the FireCMS UI.
save_property5 of 5 parameters describedAdd or update a single property in a collection schema, leaving the other properties as they are. A new property is added at the end of the display order. Example property: { "dataType": "string", "name": "Description", "description": "Product description", "multiline": true, "validation": { "required": true, "max": 500 } }
delete_property4 of 4 parameters describedRemove a property from a collection schema. This removes the field definition from the CMS configuration — it does NOT delete the field from existing Firestore documents.
generate_collection2 of 2 parameters describedGenerate a new FireCMS collection schema using AI. Provide a natural language description of the collection you want (e.g., "A blog with posts that have title, body, author, tags, and a featured image"). Returns a complete FireCMS collection configuration.
modify_collection3 of 3 parameters describedModify an existing FireCMS collection schema using AI. Describe the changes you want (e.g., "Add a priority enum with low/medium/high" or "Make title required with max 100 chars"). Returns the updated schema and a list of operations performed.
list_documents7 of 7 parameters describedList documents from a Firestore collection, with optional filters, ordering and a limit.
get_document4 of 4 parameters describedGet a specific document by its collection path and ID. Returns all fields of the document.
create_document5 of 5 parameters describedCreate a new document in a Firestore collection. Provide the field values as a JSON object.
update_document5 of 5 parameters describedUpdate fields of an existing document. Only the specified fields are modified (partial update / merge).
delete_document4 of 4 parameters describedDelete a document from Firestore. This action is permanent.
count_documents3 of 3 parameters describedCount the total number of documents in a Firestore collection.
export_collection4 of 4 parameters describedExport documents from a Firestore collection as JSON. Useful for data backups, analysis, or migration. For large collections, use the limit parameter.
import_documents5 of 5 parameters describedBulk import documents into a Firestore collection, for seeding data, migrations or restoring a backup. Each document can specify an ID; without one, Firestore generates it. By default a document with an existing ID is overwritten; with merge: true its fields are merged instead. At most 500 documents per call.
firecms_loginno parametersSign in to FireCMS Cloud. Opens a browser window for Google OAuth authentication. Required before using any other tools.
firecms_logoutno parametersSign out of FireCMS Cloud. Revokes the current session.
Tested in a sandbox with an empty environment: no API keys, a throwaway folder, nothing from a real account. A passing test shows the server runs and responds. It is not a security audit.