# FireCMS Cloud [Health: Active]

**Category:** 💻 Developer Tools  
**Repository:** https://github.com/firecmsco/firecms  
**GitHub Stars:** 1280  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/firecms-cloud

## Description
Manage FireCMS Cloud from an AI agent: Firestore data, collections, schemas and users.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "firecms-cloud": {
    "command": "npx",
    "args": ["-y","create-firecms-app"]
  }
}
```

## Documentation

## What FireCMS Cloud MCP server does

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.

## Tools and capabilities

The available capability areas described by the listing are:

- Manage Firestore data.
- Manage FireCMS collections.
- Manage schemas.
- Manage users.

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.

## How it works

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.

## Limitations and notes

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.

_Full upstream README: https://allmcps.com/mcp/firecms-cloud/readme_