Firebase MCP server for interacting with Firebase services through the Model Context Protocol
Firebase MCP server for interacting with Firebase services through the Model Context Protocol. Exposed over MCP by the firebase mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.
MCP Servers can be installed manually or at runtime via npx (recommended). How you install determines your configuration:
MCP_TRANSPORT on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.
Everything the assistant can do here goes through one of these:
firestore_add_document — Add a document to a collectionfirestore_list_documents — List documents with filteringfirestore_get_document — Get a specific documentfirestore_update_document — Update an existing documentfirestore_delete_document — Delete a documentfirestore_list_collections — List root collectionsfirestore_query_collection_group — Query across subcollectionsstorage_list_files — List files in a directorystorage_get_file_info — Get file metadata and URLstorage_upload — Upload file from contentstorage_upload_from_url — Upload file from URLauth_get_user — Get user by ID or emailYou will need 5 environment variables: SERVICE_ACCOUNT_KEY_PATH, FIREBASE_STORAGE_BUCKET, DEBUG_LOG_FILE, MCP_HTTP_HOST, MCP_HTTP_PATH. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Plenty of team communication servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Firebase's toolset — firestore_add_document, firestore_list_documents, firestore_get_document and 11 more — is a fair guide to whether it matches your workflow. It is maintained by gannonh; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| firestore_add_document | Add a document to a collection |
| firestore_list_documents | List documents with filtering |
| firestore_get_document | Get a specific document |
| firestore_update_document | Update an existing document |
| firestore_delete_document | Delete a document |
| firestore_list_collections | List root collections |
| firestore_query_collection_group | Query across subcollections |
| storage_list_files | List files in a directory |
| storage_get_file_info | Get file metadata and URL |
| storage_upload | Upload file from content |
| storage_upload_from_url | Upload file from URL |
| auth_get_user | Get user by ID or email |
| Prerequisites | The Prerequisites tool exposed by this server. |
| Required | The Required tool exposed by this server. |
{
"mcpServers": {
"firebase-1": {
"command": "npx",
"args": ["-y", "MCP_TRANSPORT"],
"env": {
"SERVICE_ACCOUNT_KEY_PATH": "your-value",
"FIREBASE_STORAGE_BUCKET": "your-value",
"DEBUG_LOG_FILE": "your-value",
"MCP_HTTP_HOST": "your-value",
"MCP_HTTP_PATH": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| SERVICE_ACCOUNT_KEY_PATH | Credential the server authenticates with. | Yes |
| FIREBASE_STORAGE_BUCKET | Configuration value read at startup. | Optional |
| DEBUG_LOG_FILE | Configuration value read at startup. | Optional |
| MCP_HTTP_HOST | Endpoint or connection string the server talks to. | Optional |
| MCP_HTTP_PATH | Filesystem location the server is allowed to use. | Optional |
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.
Inbox intelligence — search, read, draft and send Gmail through your assistant with OAuth auto-setup.
Read and write Jira, Confluence, Bitbucket, JSM and Compass from your AI client — with your own permissions.
Read and send Telegram messages through your assistant — chats, channels and history via the client API.
Enables Discord bot integration with Model Context Protocol (MCP) compatible applications like Claude Desktop.
Exposes REST APIs defined by OpenAPI specifications as Model Context Protocol (MCP) tools, facilitating seamless integration into MCP-based workflows.