Developer · Remote MCP server
FireCMS Cloud
Manage FireCMS Cloud from an AI agent: Firestore data, collections, schemas and users.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
co.firecms/mcp- Version
- 3.5.1
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP, stdio (local process)
- Package
- npm
- Published
- 2026-09-30
- Updated
- 2026-09-30
- Publisher
- co.firecms
- Namespace
- Namespace verified by the MCP Registry via the domain firecms.co · how
- Listed under
- Firebase MCP servers
- Website
- firecms.co/docs/cloud/mcp_server
- Repository
- github.com/firecmsco/firecms (folder packages/mcp_server)
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://api.firecms.co/mcp | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
- Checked on
- 2026-10-05
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | @firecms/mcp-server | 3.5.1 | stdio |
How to connect FireCMS Cloud
FireCMS Cloud is a remote MCP server: there is nothing to install. Its endpoint is https://api.firecms.co/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
It can also run locally from a Node.js package published to the npm registry: @firecms/mcp-server version 3.5.1. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y @firecms/mcp-server@3.5.1.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"mcp": {
"command": "npx",
"args": [
"-y",
"@firecms/mcp-server@3.5.1"
]
}
}
}Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| FineDataFineData web scraping MCP - JavaScript rendering, captcha solving, markdown for AI agents. | Remote & Local · HTTP, stdioLive check: sign-in required |
| FinishKit MCPFinishKit MCP: scan GitHub repos for security vulnerabilities, deployment blockers, and quality. | Local · stdio |
| Firebase Deploy Leak AuditReads firebase.json and names the files your next firebase deploy would publish to the open web. | Local · stdio |
| Firebase MCP ServerMCP server for Firebase - Firestore, Storage, Auth, and Cloud Logging, with schema validation. | Local · stdio |
| Firefox Css ThemeMCP for building, inspecting, and live-debugging Firefox CSS themes. | Local · stdio |
| Firestore Rules GuardAudits firestore.rules and storage.rules for public access, expired test-mode dates and missing owne. | Local · stdio |
| FireweedAgent memory where every fact carries a receipt, and deletion is provable. | Local · stdio |
| FireworksInspect Fireworks AI models, deployments, datasets and fine-tuning jobs. | Remote · HTTPLive check: ✓ handshake |