Firebase MCP plugin fails to start on macOS with ENOENT: resources/lib

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

The Firebase MCP plugin fails to start after installation.

The MCP server shows “Error - Show Output” and immediately disconnects. The logs indicate that npm is trying to access a non-existent directory:

/Applications/Cursor.app/Contents/Resources/app/resources/lib

This causes the Firebase MCP connection to fail before authentication or Firebase project initialization occurs.

Steps to Reproduce

  1. Install the Firebase plugin from the Cursor Marketplace.
  2. Choose either:
    • Add to Project
    • Add for Myself
  3. Open Settings > MCP Servers.
  4. Enable the Firebase MCP server.
  5. Observe that the MCP server enters an error state and fails to connect.

The issue is reproducible every time.

Expected Behavior

The Firebase MCP server should start successfully, authenticate with Firebase, and expose Firebase/Crashlytics tools within Cursor.

Operating System

MacOS

Version Information

Cursor Version: 3.10.20
VS Code Extension API: 1.125.0
Commit: 23b9fb205fe595ea2be29da7214e19762d037fc0
Build Type: Stable
Electron: 40.10.3
Chromium: 144.0.7559.236
Node.js (Cursor): 24.15.0
OS: Darwin arm64 25.5.0

Terminal Environment:
Node.js: v20.19.4
npm: 10.8.2
firebase-tools: 15.22.4
``

Additional Information

Firebase MCP output:

npm error code ENOENT
npm error syscall lstat
npm error path /Applications/Cursor.app/Contents/Resources/app/resources/lib
npm error errno -2
npm error enoent ENOENT: no such file or directory, lstat ‘/Applications/Cursor.app/Contents/Resources/app/resources/lib’

Connection failed: MCP error -32000: Connection closed

Does this stop you from using Cursor

No - Cursor works, but with this issue

Hi @Maha_Y!

Thanks for reporting. This is a known issue. Some workarounds are listed here:

I’ll also attach your report to our internal bug report, where we’re tracking this issue.