FireCMS MCP Server
FireCMS Cloud MCP server: an agent reads Firestore data, infers collection schemas and manages the project's users.
- 1,283 ★ on the repository
- Last commit
Broad access
Why this level
- Write tools change and delete documents, collection schemas and users of a live Firebase project.
- The Google sign-in and the project service account give the agent access to the client's Firestore data.
Install
- Works in
Manual install
claude mcp add --transport http firecms https://api.firecms.co/mcpHosted endpoint from the README, OAuth sign-in in the browser.
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- Write tools change and delete documents, collection schemas and users of a live Firebase project.
- The Google sign-in and the project service account give the agent access to the client's Firestore data.
This is third-party code. Review the repository files before installing.
What it does
Hosted FireCMS Cloud is a back office for Firebase projects, and the MCP server from the FireCMS repository connects an agent to it. The agent lists Firestore root collections and nested documents, reads and edits records, and changes a project's name, colors and default locale. The main scenario is connecting a project that already holds data. `preview_inferred_schema` samples up to 200 documents of a collection and shows a draft schema without saving anything. `setup_all_collections` infers schemas for every root collection, and separate tools invite users and change their roles. The server runs in two ways. The hosted endpoint `https://api.firecms.co/mcp` needs no install and signs in through OAuth in the browser. The local one starts with `npx @firecms/mcp-server`, signs in with a Google account, and can enable APIs, create a Firestore database and connect the project itself.
Who it is for. Firebase developers who want a ready admin panel over an existing Firestore database without describing every collection by hand.
Good fit when
- Dozens of collections already sit in Firestore, and inferring CMS schemas from the data beats writing them by hand.
- Editors need access to content, and project user roles are easier to hand out from a chat with an agent.
- A new Firebase project is connected to FireCMS end to end: enable APIs, create the database, apply security rules.
- A draft schema built from real documents is worth reviewing and tweaking before it is saved.
Not a fit when
- FireCMS runs self-hosted as a library rather than in the cloud: the server works only with FireCMS Cloud.
- The agent should only read: writes need the project admin role, and the server has no separate read-only mode.
- The database needs bulk document migrations: the tools are built for CMS setup, not for moving data.
Example request
List the project's root collections and infer a schema for the `orders` collection from its first 200 documents without saving it.MCP
- Transport
- http, stdio
- Authentication
- OAuth
Limitations
All write operations require the project admin role. The hosted endpoint does not connect a new Firebase project itself and returns a link to the web app. Enable Firebase Authentication in the Firebase console before connecting, since that step has no API. The local server keeps sign-in tokens in `~/.firecms/tokens.json`, a file shared with the FireCMS CLI. Role checks are cached for 5 minutes, so a fresh permission change may apply with a delay. The server works with FireCMS Cloud only and does not cover a self-hosted FireCMS.
How to disable. Remove the `firecms` server from the client settings, which in Claude Code is `claude mcp remove firecms`. The local sign-in ends with the `firecms_logout` tool, and the granted access is revoked in the Google account.
FAQ
How do I connect FireCMS to Claude Code?
Run `claude mcp add --transport http firecms https://api.firecms.co/mcp`. The first call opens the browser for the OAuth sign-in, and nothing needs installing.
How does the hosted endpoint differ from the local server?
The hosted endpoint connects without an install but does not create a Firestore database or enable Google Cloud APIs. The local `npx @firecms/mcp-server` signs in with `firecms_login` and takes a project from enabling APIs to finished collections.
Can I give the agent read-only access?
Yes, by signing in as a project member without the admin role. Reads work for that member, and any write is rejected.
What does setup_all_collections do?
It samples documents in every root collection, determines field types and picks names and icons with a language model. It skips paths that are already mapped, so running it again is safe.
What Firestore data does the agent see?
The agent reads documents through the FireCMS backend with the project's delegated service account. The project list comes without service account credentials, so they never reach the model context.
Discussion
No questions or reviews yet.
Related
MCP serversFirebase MCP Server
Firebase CLI and MCP Server
Official Firebase MCP server from the Firebase CLI: projects, Firestore, Auth, Crashlytics, Remote Config and function logs
Firenook replaces the Firebase emulator with a fast native engine and gives agents MCP access to Firestore, Auth and Storage.
MCP server for the InsForge backend: the agent creates tables, buckets and edge functions and ships the app from the editor
A single Go binary turns a SQL database into a REST API with roles and an MCP server for Claude Code, Cursor and VS Code
Apollo's MCP server: turns chosen GraphQL operations into tools the agent uses to work with your API
Supabase's official MCP server: the agent manages tables, reads project config and queries data after an OAuth login
README in short
The README covers hosted and local startup, the order for connecting a Firebase project and tables of tools by group: auth, onboarding, schemas, users and data. It ends with the authorization scheme and token storage.