Firebase MCP vs Moxie Docs MCP
A side-by-side look at the Firebase MCP and Moxie Docs MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Firebase MCP for databases work as a local process; choose Moxie Docs MCP for knowledge & memory as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Firebase MCP when
- You need dedicated capabilities in the Databases domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: other.
- You have the keys it needs:
SERVICE_ACCOUNT_KEY_PATH, FIREBASE_STORAGE_BUCKET, MCP_TRANSPORT, MCP_HTTP_PORT, MCP_HTTP_HOST, MCP_HTTP_PATH, DEBUG_LOG_FILE.
Choose Moxie Docs MCP when
- You need dedicated capabilities in the Knowledge & Memory domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You want tools like
moxie.get_ai_context, moxie.get_doc_impact, moxie.get_api_context.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Databases | Knowledge & Memory |
| Quality signal | 47/100 · Fair | 80/100 · Excellent |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | other | API key required |
| Pricing | Free | Freemium |
| Required env vars | SERVICE_ACCOUNT_KEY_PATHFIREBASE_STORAGE_BUCKETMCP_TRANSPORTMCP_HTTP_PORTMCP_HTTP_HOSTMCP_HTTP_PATHDEBUG_LOG_FILE | None listed |
| Verified owner | Community listing | Verified |
| GitHub stars | 247 | 2 |
| Directory activity | 2 views 0 installs 0 upvotes | 36 views 25 installs 4 upvotes |
| Tools | Not listed | 12 |
| Full listing | View Firebase MCP | View Moxie Docs MCP |
Tools & capabilities
Firebase MCP tools
No tool names declared yet. Check the project README from the listing page.
Moxie Docs MCP tools 12
moxie.get_ai_contextCompact pre-edit briefing: repo status, verified commands, top conventions, open gaps, team notes. Read this first.moxie.get_doc_impactGiven the paths you're about to change (and any you're deleting), returns the conventions, gaps, and existing docs whose evidence overlaps them - and flags net-new/undocumented surfaces.moxie.get_api_contextGiven paths you're about to touch, returns structured context for any API endpoints they map to: method, path, schema, and known consumers/features.moxie.review_changeSelf-review a change before opening the PR; returns a severity-ranked verdict (clean / warnings / must-fix) covering convention breaches, stale docs, undocumented surface, and broken references.moxie.get_conventionsDiscovered coding conventions, grouped by category, with confidence scores, agent guidance, and source-file citations.moxie.search_docsSemantic + keyword search over generated docs, conventions, gaps, and AI context.moxie.get_doc_gapsUnresolved documentation gaps with severity and the paths they concern.moxie.get_documentation_opportunitiesRecommended doc work: missing docs, drift repairs, and PR templates.moxie.get_documentation_patternsHow the repository organizes and maintains its docs (where new docs belong).moxie.list_docsPaginated, section-grouped table of contents of every generated doc.moxie.propose_doc_updateAdd or update a doc as part of your current change; returns the target path + Markdown to write into your branch.moxie.propose_doc_removalRemove a Moxie-tracked doc your change makes obsolete; returns the path to delete in your branch.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Firebase MCP
{
"mcpServers": {
"gannonh-firebase-mcp": {
"command": "npx",
"args": [
"-y",
"@gannonh/firebase-mcp"
],
"env": {
"SERVICE_ACCOUNT_KEY_PATH": "YOUR_SERVICE_ACCOUNT_KEY_PATH_HERE",
"FIREBASE_STORAGE_BUCKET": "YOUR_FIREBASE_STORAGE_BUCKET_HERE",
"MCP_TRANSPORT": "YOUR_MCP_TRANSPORT_HERE",
"MCP_HTTP_PORT": "YOUR_MCP_HTTP_PORT_HERE",
"MCP_HTTP_HOST": "YOUR_MCP_HTTP_HOST_HERE",
"MCP_HTTP_PATH": "YOUR_MCP_HTTP_PATH_HERE",
"DEBUG_LOG_FILE": "YOUR_DEBUG_LOG_FILE_HERE"
}
}
}
}
Moxie Docs MCP
{
"mcpServers": {
"moxie-docs-mcp": {
"command": "npx",
"args": [
"-y",
"moxie-docs"
]
}
}
}
Frequently asked questions
Firebase MCP is categorized under Databases and uses a local stdio subprocess. Moxie Docs MCP belongs to Knowledge & Memory and uses a local stdio subprocess. Pick Firebase MCP for databases work and Moxie Docs MCP for knowledge & memory.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Firebase MCP is listed as free. Auth: other. Moxie Docs MCP is listed as freemium — a free tier with paid plans. Auth: api key required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add gannonh-firebase-mcp and moxie-docs-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Firebase MCP has a quality signal of 47/100 (Fair) with 2 views, 0 installs and 247 GitHub stars. Moxie Docs MCP has 80/100 (Excellent) with 36 views, 25 installs and 2 GitHub stars.