Manage Firestore data, collections, schemas, and users in FireCMS Cloud through an AI agent.
Copy the AI prompt to install this server into Claude Code, Cursor, or another agent โ or use 1-click editor setup below.
We haven't yet run this listing's install command through our automated sandbox check. This isn't a red flag โ we're steadily working through the catalog.
๐ก Paste the JSON block into your client's configuration file under mcpServers, then restart the application.
Inspect callable tools, capabilities, and parameters exposed to AI agents by FireCMS Cloud.
The FireCMS Cloud MCP server gives an AI agent access to core FireCMS Cloud administration areas. The supplied description identifies four areas: Firestore data, collections, schemas, and users. This makes the server relevant to projects that use FireCMS Cloud as a managed administration layer over Firebase and Firestore.
FireCMS itself is an open-source Firebase CMS and Firestore admin panel framework built with React and TypeScript. Its Cloud edition is hosted and managed, while the broader project also supports self-hosted deployments. The MCP listing is specifically about managing the Cloud product from an AI agent rather than building a custom FireCMS application.
The available capability areas described by the listing are:
These capabilities map to common FireCMS administration tasks. FireCMS documentation also describes collection views, schema management, role-based permissions, and user management as product areas, but the supplied material does not provide individual MCP tool names, argument formats, return values, or operation-level permissions. Treat the four listed areas as the supported scope rather than assuming every FireCMS feature is exposed through MCP.
An AI agent uses the FireCMS Cloud MCP server as the interface for work in a FireCMS Cloud project. Requests are directed at Firestore content or FireCMS configuration resources, allowing the agent to work with data and administrative entities through the server instead of requiring a person to perform each action in the web application.
The provided material does not explain whether the server uses stdio, streamable HTTP, or another MCP transport. It also does not describe authentication, project selection, confirmation behavior, or how changes are reported to the agent. Those details should be verified before deployment, especially for workflows that modify production data or user access.
The FireCMS Cloud MCP server should not be treated as a complete description of the FireCMS product. The repository README covers the wider FireCMS framework, including self-hosting, Firebase Storage, import and export, audit history, AI features, and custom React extensions. The listing only confirms agent management for Firestore data, collections, schemas, and users.
No MCP installation command, configuration example, environment variable, client compatibility list, or detailed API reference appears in the supplied material. The excerpt also does not state whether the server can connect to MongoDB; FireCMS supports MongoDB in some editions, but the Cloud edition table marks MongoDB support as unavailable.
Factual signals from GitHub, npm, and our automated checks โ not a rating.
No reviews yet โ be the first to share how this listing worked for you.
Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.
[](https://allmcps.com/mcp/firecms-cloud)<a href="https://allmcps.com/mcp/firecms-cloud"><img src="https://allmcps.com/api/badge/firecms-cloud?style=directory" alt="FireCMS Cloud on AllMCPs" /></a>