🐛 Summary
MCP server crashes on startup with the following error:
Error: Cannot find module 'googleapis'
Require stack:
- .../node_modules/firebase-tools/lib/mcp/tools/apptesting/tests.js
- .../node_modules/firebase-tools/lib/mcp/tools/apptesting/index.js
- .../node_modules/firebase-tools/lib/mcp/tools/index.js
- .../node_modules/firebase-tools/lib/mcp/index.js
💡 Bug Information
| Item |
Details |
| Affected Tool(s) |
All MCP tools using App Testing functionality |
| MCP Client |
Claude Code |
| Operating System |
macOS Tahoe (affects all platforms) |
| firebase-tools version |
14.24.1 (latest) |
| Node.js version |
20.x / 22.x |
⚙️ Steps to Reproduce
-
Install Firebase MCP using the official command:
npx -y firebase-tools@latest mcp
-
Start the MCP server — it fails immediately with the error above.
🔍 Root Cause
The module googleapis is listed under devDependencies
but it’s used in production MCP code:
lib/mcp/tools/apptesting/tests.js
When installing via npx, dev dependencies are not included, leading to a runtime failure.
✅ Expected Behavior
The MCP server should start successfully with all required dependencies available.
🛠️ Suggested Fix
Move the googleapis package from devDependencies to dependencies in package.json.
🧩 Environment
- firebase-tools: 14.24.1
- Node.js: 20.x / 22.x
- OS: macOS Tahoe (but reproducible cross-platform)
❓ Question
Am I missing something in the setup, or is this a packaging bug?
🐛 Summary
MCP server crashes on startup with the following error:
💡 Bug Information
14.24.1(latest)20.x/22.x⚙️ Steps to Reproduce
Install Firebase MCP using the official command:
Start the MCP server — it fails immediately with the error above.
🔍 Root Cause
The module
googleapisis listed underdevDependenciesbut it’s used in production MCP code:
When installing via
npx, dev dependencies are not included, leading to a runtime failure.✅ Expected Behavior
The MCP server should start successfully with all required dependencies available.
🛠️ Suggested Fix
Move the
googleapispackage fromdevDependenciestodependenciesinpackage.json.🧩 Environment
❓ Question
Am I missing something in the setup, or is this a packaging bug?