# FireCMS Cloud — MCP server card for AI agents

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

Registry name: `co.firecms/mcp` · category: Databases · version 3.5.3 · updated 2026-11-15

## Connect
- npm (stdio): `npx -y @firecms/mcp-server`
- Remote (Claude Code): `claude mcp add --transport http firecms-cloud https://api.firecms.co/mcp`

## Facts
- Repository: https://github.com/firecmsco/firecms (1,284 stars)
- Website: https://firecms.co/docs/cloud/mcp_server

Before you connect a server: read its repository, and give it only the permissions and keys it needs.

## Links
- AgentGid page: https://agentgid.com/mcp/servers/co-firecms-mcp/


## FireCMS Cloud: run your Firebase admin panel by chat

FireCMS Cloud turns the data in a Firebase database into an admin panel where your team edits content. With this server your AI assistant works in that panel for you. It can browse and edit records, add fields, build sections from data you already have and invite people, always with your own account's rights.

### Where to use it
- An admin panel for an existing app: Your app already stores products or posts in Firebase. Your assistant connects the project and builds an editing screen for each kind of data from the records already there.
- Add a field by asking: Ask for a new "featured" switch on products, shown after the title, and the editing screen gets it without you touching any settings.
- A new section with starter data: Describe a new section, like a list of events, and your assistant creates it and fills it with your first records.
- Edit content in plain words: Ask to find the posts still marked draft and publish three of them, or to fix a typo in one product name.
- Who can edit what: Invite an editor, change someone's role or remove a person who left, from the chat.
- A quick data export: Get one section's records as a file to check them in a spreadsheet or hand them to someone.

### How to start
- Add the hosted server, then run /mcp in Claude Code and choose Authenticate; FireCMS Cloud opens in the browser for sign-in.

```
claude mcp add --transport http firecms https://api.firecms.co/mcp
```

- Ask for your projects first; every other tool takes a project id from that list.
- To let the agent also enable Google Cloud services and create the database, run the server locally and sign in with Google.

```
claude mcp add firecms -- npx -y @firecms/mcp-server
```


### License
This server's code is MIT licensed, so you can use it in paid work and keep the notice if you pass it on. Other parts of the FireCMS project use other licenses. Using FireCMS Cloud itself needs a FireCMS Cloud account.

### Good to know
- You need a FireCMS Cloud account. Any project member can read, but creating or changing data, sections and users needs the admin role.
- The tools read and write through the project's own service account, which skips your database security rules. So the assistant can delete or overwrite any record your admin role allows.
- Creating the database fixes its location for good, so choose the region before you say yes.
- The hosted server cannot connect a new Firebase project by itself. It gives you a link to finish that step in the FireCMS web app.
- FireCMS Cloud is free to start and needs no credit card, as the vendor reports.

Checked 2026-11-10 against: https://firecms.co/docs/cloud/mcp_server, https://github.com/firecmsco/firecms/blob/b0e474ddf46149c95532dd40c853531c0f17e0c6/packages/mcp_server/README.md, https://github.com/firecmsco/firecms/blob/b0e474ddf46149c95532dd40c853531c0f17e0c6/packages/mcp_server/package.json, https://github.com/firecmsco/firecms/blob/b0e474ddf46149c95532dd40c853531c0f17e0c6/packages/mcp_server/server.json, https://github.com/firecmsco/firecms/blob/b0e474ddf46149c95532dd40c853531c0f17e0c6/packages/mcp_server/src/server.ts, https://github.com/firecmsco/firecms/blob/b0e474ddf46149c95532dd40c853531c0f17e0c6/LICENSE, https://registry.npmjs.org/@firecms%2fmcp-server, https://github.com/firecmsco/firecms/releases/tag/v3.5.1

### Mistakes to avoid
- Don't: infer_collections_from_data on a path that has no documents yet → Do: Infer only paths with data; define new collections with save_collection_schema (With nothing to sample, the model invents fields from the path name alone.)
- Don't: save_collection_schema to change one field → Do: save_property or update_collection_schema for one field; save_collection_schema replaces the whole schema (save_collection_schema creates or replaces the schema.)
- Don't: connect_project_to_firecms before Firebase Authentication is on → Do: Ask the person to turn on Authentication in the Firebase console first (It has no API, and without it the CMS opens nothing.)
- Don't: import_documents with thousands of records in one call → Do: Split the import into calls of at most 500 documents (The import tool takes at most 500 documents per call.)
- Don't: Call other tools before list_projects → Do: Call list_projects first and take the projectId from it (Every other tool needs a projectId.)

### Questions
- Do I have to install anything? No for the hosted server; add its address and sign in to FireCMS Cloud in the browser. The local server needs Node.js 18 or later.
- Can the assistant do more than I can? No. It acts with your own account, and every write checks the admin role on that project.
- Does deleting a collection schema delete my data? No. delete_collection_schema removes the schema and leaves the data untouched; delete_document does delete records.
- Will my Google Cloud credentials end up in the chat? No. list_projects removes each project's service account from its output.

---
AgentGid's catalog is curated: every entry was checked against the maker's official pages (registry, repository, license and pricing pages) on the date shown; a license value shows the quote it stands on wherever AgentGid has one. Usage numbers come from AgentGid's own scan of public repositories set up for AI coding agents. Claims by makers are reported, not tested by AgentGid.
