MCP server for FireCMS Cloud — manage projects, collections, users, and AI features via the Model Context Protocol
Inferred from the transports this listing declares (stdio, streamable-http). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.
firecms_loginSign in to FireCMS Cloud. Opens a browser window for Google OAuth authentication. Required before using any other tools.Sign in to FireCMS Cloud. Opens a browser window for Google OAuth authentication. Required before using any other tools.
No input schema was published for this tool.
firecms_logoutSign out of FireCMS Cloud. Revokes the current session.Sign out of FireCMS Cloud. Revokes the current session.
No input schema was published for this tool.
list_collection_schemasList 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.List 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.
No input schema was published for this tool.
get_collection_schemaGet the full schema definition for a specific collection, including all properties,
validation rules, display configuration, and subcollection definitions.Get the full schema definition for a specific collection, including all properties, validation rules, display configuration, and subcollection definitions.
No input schema was published for this tool.
save_collection_schemaNo description publishedThis tool published no description. Forge does not invent one.
update_collection_schemaPartially 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.Partially 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.
No input schema was published for this tool.
delete_collection_schemaprivilegedDelete 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.Delete 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.
No input schema was published for this tool.
save_propertyAdd 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.Add 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.
No input schema was published for this tool.
delete_propertyprivilegedRemove 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.Remove 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.
No input schema was published for this tool.
generate_collectionGenerate 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.Generate 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.
No input schema was published for this tool.
modify_collectionModify 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.Modify 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.
No input schema was published for this tool.
firecms_get_current_userGet the currently authenticated FireCMS userGet the currently authenticated FireCMS user
No input schema was published for this tool.
list_documentsList documents from a Firestore collection, with optional filters, ordering and a limit.List documents from a Firestore collection, with optional filters, ordering and a limit.
No input schema was published for this tool.
get_documentGet a specific document by its collection path and ID. Returns all fields of the document.Get a specific document by its collection path and ID. Returns all fields of the document.
No input schema was published for this tool.
create_documentCreate a new document in a Firestore collection. Provide the field values as a JSON object.Create a new document in a Firestore collection. Provide the field values as a JSON object.
No input schema was published for this tool.
update_documentUpdate fields of an existing document. Only the specified fields are modified (partial update / merge).Update fields of an existing document. Only the specified fields are modified (partial update / merge).
No input schema was published for this tool.
delete_documentprivilegedDelete a document from Firestore. This action is permanent.Delete a document from Firestore. This action is permanent.
No input schema was published for this tool.
count_documentsCount the total number of documents in a Firestore collection.Count the total number of documents in a Firestore collection.
No input schema was published for this tool.
export_collectionExport documents from a Firestore collection as JSON. Useful for data backups,
analysis, or migration. For large collections, use the limit parameter.Export documents from a Firestore collection as JSON. Useful for data backups, analysis, or migration. For large collections, use the limit parameter.
No input schema was published for this tool.
import_documentsBulk 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 document…Bulk 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 document…
No input schema was published for this tool.
list_databasesList the Firestore databases of a project. Only needed for projects using moreList the Firestore databases of a project. Only needed for projects using more
No input schema was published for this tool.
preview_inferred_schemaRead 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.Read 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.
No input schema was published for this tool.
infer_collections_from_dataInfer collections from the existing Firestore data at the given paths, and save them to the project. Requires admin.Infer collections from the existing Firestore data at the given paths, and save them to the project. Requires admin.
No input schema was published for this tool.
setup_all_collectionsDiscover 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.Discover 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.
No input schema was published for this tool.
connect_project_to_firecmsGet the link to connect a Firebase project to FireCMS Cloud.Get the link to connect a Firebase project to FireCMS Cloud.
No input schema was published for this tool.
list_firebase_projectsList the Google Cloud / Firebase projects the signed-in user can access, and whether each one is ready to be connected to FireCMS Cloud.List the Google Cloud / Firebase projects the signed-in user can access, and whether each one is ready to be connected to FireCMS Cloud.
No input schema was published for this tool.
get_project_setup_statusGet 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.Get 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.
No input schema was published for this tool.
list_firestore_locationsList the locations available for a new Firestore database, as location IDs such as 'eur3' or 'us-central'.List the locations available for a new Firestore database, as location IDs such as 'eur3' or 'us-central'.
No input schema was published for this tool.
enable_project_apisEnable the Google Cloud APIs that FireCMS requires on a project (reported as `apisEnabled` in its setup status). Safe to run more than once.Enable the Google Cloud APIs that FireCMS requires on a project (reported as `apisEnabled` in its setup status). Safe to run more than once.
No input schema was published for this tool.
enable_firestoreCreate the default Firestore database in a Google Cloud project, in the given location. The location is permanent and cannot be changed later.Create the default Firestore database in a Google Cloud project, in the given location. The location is permanent and cannot be changed later.
No input schema was published for this tool.
apply_firestore_security_rulesAdd FireCMS's access rule to a project's Firestore and Storage security rules. Requires admin.Add FireCMS's access rule to a project's Firestore and Storage security rules. Requires admin.
No input schema was published for this tool.
create_firecms_webappCreate 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.Create 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.
No input schema was published for this tool.
get_project_configGet 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 infoGet 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
No input schema was published for this tool.
update_project_nameUpdate the display name of a FireCMS project.Update the display name of a FireCMS project.
No input schema was published for this tool.
update_project_colorsUpdate the primary and/or secondary brand colors for the CMS UI. Colors should be hex values (e.g., '#0070F4').Update the primary and/or secondary brand colors for the CMS UI. Colors should be hex values (e.g., '#0070F4').
No input schema was published for this tool.
update_default_localeChange the default locale for the CMS (affects date formatting, etc.).Change the default locale for the CMS (affects date formatting, etc.).
No input schema was published for this tool.
toggle_text_searchEnable or disable the local text search feature for a project.Enable or disable the local text search feature for a project.
No input schema was published for this tool.
toggle_entity_historyEnable or disable entity history tracking (audit log of document changes) for a project.Enable or disable entity history tracking (audit log of document changes) for a project.
No input schema was published for this tool.
list_projectsList all FireCMS Cloud projects accessible by the authenticated userList all FireCMS Cloud projects accessible by the authenticated user
No input schema was published for this tool.
get_root_collectionsList all Firestore root-level collections in a FireCMS project — theList all Firestore root-level collections in a FireCMS project — the
No input schema was published for this tool.
39 of 40 tools published a description.
Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.
MCP server for FireCMS Cloud — manage projects, collections, users, and AI features via the Model Context Protocol
Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.
The crawl stopped at the 60-package limit. The rest of the tree was never resolved.
36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)
105 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.
+93 more not listed. The counts by reason above cover all of them.
Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.