FireCMS Cloud

FireCMS's own MCP server for FireCMS Cloud, the CMS for Firebase. It lets your agent work on your FireCMS project: browse and edit Firestore data, turn the documents already in Firestore into collections, shape collection schemas and properties, configure the project and manage its users. The agent acts with your own FireCMS account, so it can't do anything you couldn't do yourself in FireCMS Cloud. What you can do with it - List your FireCMS Cloud projects, and the root collections and subcollections in their Firestore - Query, read, create, update, delete and count documents, export a collection as JSON, and import documents in bulk (up to 500 per call) - Turn an existing Firestore database into a CMS: preview a schema inferred from sampled documents without saving it, or infer and save every root collection that isn't mapped yet - Create and change collection schemas and single properties, or have FireCMS generate or modify a schema from a description - Rename a project, change its brand colours and default locale, and turn text search and entity history on or off - List, invite and remove users, and change their roles How it connects - Hosted: add https://api.firecms.co/mcp to your agent and sign in to FireCMS Cloud in the browser. There's nothing to install. In Claude, add it as a custom connector; in Claude Code, run claude mcp add --transport http firecms https://api.firecms.co/mcp, then /mcp and Authenticate. - Local: npx -y @firecms/mcp-server runs the same server on your machine (Node.js 18 or later). Ask your agent to run the firecms_login tool: it signs in with your Google account in the browser and stores the credentials in ~/.firecms/tokens.json, shared with the FireCMS CLI. - Connecting a new Firebase project: the local server can do it end to end (enable the Google Cloud APIs, create the Firestore database and connect it). The hosted server holds no Google Cloud credentials, so it hands that one step to the FireCMS Cloud web app. Permissions - Any project member can read data. Writes, and the project's settings, schemas and users, need the admin role on that project. - Every tool tells your agent whether it only reads, and whether a change can overwrite or delete, so agents that ask before writing know when to ask. - Service account credentials are stripped from the project list, so they never reach the model. Good to know - You need a FireCMS Cloud account, and Firebase Authentication must be enabled on a project before you connect it. - FireCMS documents setup for Claude, Claude Code and Cursor; the hosted address works in any agent that takes remote MCP servers by URL.

• “List my FireCMS projects.”

  1. list_projects
  Copy

• “List the collections in my FireCMS project.”

  1. get_root_collections
  Copy

• “Add a "featured" boolean property to the products collection, shown after the title.”

  1. save_property
  Copy

• “Turn the data already in my Firestore into FireCMS collections.”

  1. setup_all_collections
  Copy

• “Draft a schema for the orders collection from its documents, without saving it.”

  1. preview_inferred_schema
  Copy

• “Generate a blog posts collection with a title, author and publish date.”

  1. generate_collection
  2. save_collection_schema
  Copy