# FireCMS Cloud MCP server

> Manage FireCMS Cloud projects from an AI agent: Firestore data, collection schemas, project settings and users.

- Listing: https://mcp.tc/i/firecms-cloud
- Connect: use the server's own URL `https://api.firecms.co/mcp` (OAuth sign-in at the server); clients connect to it directly. The listing link is a page, not an MCP endpoint.
- Type: remote (Streamable HTTP)
- Auth: OAuth sign-in
- Category: [Databases & Backend](https://mcp.tc/c/databases)
- Vendor: FireCMS
- Homepage: <https://firecms.co/docs/cloud/mcp_server>
- Docs: <https://firecms.co/docs/cloud/mcp_server>
- Repository: <https://github.com/firecmsco/firecms/tree/HEAD/packages/mcp_server>
- Package: npm `@firecms/mcp-server`

## About

Connects an AI assistant to FireCMS Cloud, a CMS built on Firebase and Firestore. You can browse and edit Firestore data, infer collections and schemas from existing documents, edit collection properties, change project settings and manage project users. Write operations require the admin role on the target project; reads are open to any project member.

The hosted endpoint at https://api.firecms.co/mcp needs nothing installed. Clients sign in with OAuth in the browser and each client is approved in FireCMS Cloud. A local package (npx @firecms/mcp-server) is also available; it signs in with a Google account and can also enable APIs, create Firestore databases and connect projects.

## What it can do

- List Firestore root collections and subcollections
- Preview and save schemas inferred from existing data
- Create, update and delete collection schemas and properties
- Read and change project name, colors, locale and features
- List, invite, update and remove project users
- Connect a Firebase project to FireCMS (local server end to end)

## Example prompts

- "List the root collections in my FireCMS project"
- "Preview an inferred schema for the orders collection"
- "Add a user with the admin role to my FireCMS project"
- "Rename my FireCMS project and change its primary color"

## Install

### Claude Code

1. Run this in a terminal, in your project folder:

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

2. Start Claude Code, type `/mcp`, pick **firecms-cloud** and choose **Authenticate**. A browser window opens for the FireCMS sign-in.

Add `--scope user` to make it available in every project, not just this one.

### Claude Desktop

1. Open **Customize → Connectors**, click **+ Add**, then **Add custom connector**.

2. Name it **FireCMS Cloud** and paste this URL:

```url
https://api.firecms.co/mcp
```

3. Click **Add**, then **Connect**, and sign in when FireCMS asks.

Claude Desktop’s JSON config file only starts local servers. Remote servers go through Connectors, and connectors you add on claude.ai show up here too.

### claude.ai

1. Open the connector form on claude.ai. This button fills in the name and URL for you:

[Add to claude.ai](<https://claude.ai/customize/connectors?modal=add-custom-connector&connectorName=FireCMS%20Cloud&connectorUrl=https%3A%2F%2Fapi.firecms.co%2Fmcp>) (opens connector settings)

2. Check that the URL reads `https://api.firecms.co/mcp` and click **Add**.

3. Click **Connect** and sign in when FireCMS asks.

Free plans allow one custom connector. On Team and Enterprise plans an owner adds it under **Organization settings → Connectors**.

### ChatGPT

1. On chatgpt.com, go to **Plugins**, select **+**, then **Add custom MCP server**.

2. Enter a name for the server.

3. Under **Connection**, paste `https://api.firecms.co/mcp` as the server URL, then for authentication choose **OAuth**. ChatGPT sends you to FireCMS to sign in.

4. Check **I understand and want to continue**, then select **Create as a plugin**.

Whether you can add a custom MCP server depends on your ChatGPT plan and your workspace permissions (in Business workspaces, admins and owners can).

### Cursor

[Add to Cursor](<https://cursor.com/install-mcp?name=firecms-cloud&config=eyJ1cmwiOiJodHRwczovL2FwaS5maXJlY21zLmNvL21jcCJ9>) (opens Cursor)

Or add it by hand to `~/.cursor/mcp.json` (all projects) or `.cursor/mcp.json` (this project):

`mcp.json`:

```json
{
  "mcpServers": {
    "firecms-cloud": {
      "url": "https://api.firecms.co/mcp"
    }
  }
}
```

Cursor shows **Needs authentication** next to the server. Click the button beside it to sign in.

### VS Code

[Install in VS Code](<https://vscode.dev/redirect/mcp/install?name=firecms-cloud&config=%7B%22type%22%3A%22http%22%2C%22url%22%3A%22https%3A%2F%2Fapi.firecms.co%2Fmcp%22%7D>) (opens VS Code)

Or from a terminal:

```bash
code --add-mcp '{"name":"firecms-cloud","type":"http","url":"https://api.firecms.co/mcp"}'
```

Or commit it to the repo in `.vscode/mcp.json`:

`.vscode/mcp.json`:

```json
{
  "servers": {
    "firecms-cloud": {
      "type": "http",
      "url": "https://api.firecms.co/mcp"
    }
  }
}
```

VS Code asks you to sign in the first time the server starts.

### Devin Desktop

1. Add it to `~/.config/devin/mcp_config.json` (macOS and Linux) or `%APPDATA%\devin\mcp_config.json` (Windows):

`mcp_config.json`:

```json
{
  "mcpServers": {
    "firecms-cloud": {
      "serverUrl": "https://api.firecms.co/mcp"
    }
  }
}
```

2. Refresh the MCP server list in Cascade and sign in when asked.

Devin Desktop is the new name for Windsurf. It reads `serverUrl` (or `url`) for remote servers.

### Codex

```bash
codex mcp add firecms-cloud --url https://api.firecms.co/mcp
codex mcp login firecms-cloud
```

Or edit `~/.codex/config.toml` directly:

`config.toml`:

```toml
[mcp_servers.firecms-cloud]
url = "https://api.firecms.co/mcp"
```

### Gemini CLI

```bash
gemini mcp add --transport http firecms-cloud https://api.firecms.co/mcp
```

Then, inside Gemini CLI, run `/mcp auth firecms-cloud` to sign in.

This adds it to the current project. Add `-s user` to use it everywhere.

### Any client

Most clients accept this shape. Some name the URL field differently: `serverUrl` in Devin Desktop, `httpUrl` in Gemini CLI’s settings file.

```json
{
  "mcpServers": {
    "firecms-cloud": {
      "type": "http",
      "url": "https://api.firecms.co/mcp"
    }
  }
}
```

Zed puts servers under `context_servers` in its settings. Cline needs `"type": "streamableHttp"`, or it assumes SSE.

Client only starts local servers? Bridge it with `npx -y mcp-remote https://api.firecms.co/mcp`.

## Details

- Server version: 3.5.1
- Last checked: 2026-11-18 (reachable, asks for credentials)
- Listed: 2026-10-11
- Updated: 2026-10-11

---
Source: https://mcp.tc/i/firecms-cloud (mcp.tc is an independent directory, not affiliated with this server's publisher). Corrections: https://mcp.tc/report
