Firebase MCP no longer working

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

After the latest update the Firebase Plugin / MCP is no longer working.

Cursor updated June 15, 2026
Firebase MCP plugin fails with ENOENT: /Applications/Cursor.app/Contents/Resources/app/resources/lib
Worked before the update

The error is npm itself failing before it even reaches Firebase CLI.

npm error path /Applications/Cursor.app/Contents/Resources/app/resources/lib
npm error enoent ENOENT: no such file or directory
npm is looking for a directory inside Cursor.app that doesn’t exist.

2026-06-16 11:24:50.410 [info] [MCPService] [MCPService] createClient: identifier=“plugin-firebase-Firebase”, serverName=“Firebase”
2026-06-16 11:24:50.417 [info] [MCPService] [MCPService] createClient completed for server: plugin-firebase-Firebase, statusType=initializing, success=true
2026-06-16 11:24:50.420 [info] [Shared MCP process] connecting stdio for “Firebase” (plugin-firebase-Firebase)
2026-06-16 11:24:50.420 [info] [Shared MCP process] [V2 FSM] connection:connect_start: conn=idle,auth=unknown → conn=connecting,auth=unknown
2026-06-16 11:24:50.797 [error] [Shared MCP process] npm error code ENOENT
npm error syscall lstat
undefined
2026-06-16 11:24:50.797 [error] [Shared MCP process] 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’
npm error enoent This is related to npm not being able to find a file.
npm error enoent
npm error A complete log of this run can be found in: /Users/kenneth/.npm/_logs/2026-06-16T09_24_50_476Z-debug-0.log
undefined
2026-06-16 11:24:50.802 [warning] [Shared MCP process] Connection failed: MCP error -32000: Connection closed
2026-06-16 11:24:50.802 [warning] [Shared MCP process] [V2 FSM] connection:connect_failure: conn=connecting,auth=unknown → conn=failed,auth=unknown
2026-06-16 11:24:52.537 [info] [Shared MCP process] stopped connection: plugin-firebase-Firebase
2026-06-16 11:24:52.540 [info] [Shared MCP process] connecting stdio for “Firebase” (plugin-firebase-Firebase)
2026-06-16 11:24:52.540 [info] [Shared MCP process] [V2 FSM] connection:connect_start: conn=idle,auth=unknown → conn=connecting,auth=unknown
2026-06-16 11:24:52.835 [error] [Shared MCP process] npm error code ENOENT
npm error syscall lstat
undefined
2026-06-16 11:24:52.835 [error] [Shared MCP process] 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’
npm error enoent This is related to npm not being able to find a file.
npm error enoent
undefined
2026-06-16 11:24:52.835 [error] [Shared MCP process] npm error A complete log of this run can be found in: /Users/kenneth/.npm/_logs/2026-06-16T09_24_52_595Z-debug-0.log
undefined
2026-06-16 11:24:52.839 [warning] [Shared MCP process] Connection failed: MCP error -32000: Connection closed
2026-06-16 11:24:52.839 [warning] [Shared MCP process] [V2 FSM] connection:connect_failure: conn=connecting,auth=unknown → conn=failed,auth=unknown

Steps to Reproduce

Settings → Tools & MCP → Click “Reload MCP server” on Firebase

Expected Behavior

That it connects to Firebase :slight_smile:

Maybe the location changed ?

Operating System

MacOS

Version Information

Version: 3.7.36
VS Code Extension API: 1.105.1
Commit: 776d1f9d76df50a4e0aeca61819a88e7c1b861e0
Date: 2026-06-13T00:31:56.287Z
Layout: editor
Build Type: Stable
Release Track: Default
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
xterm.js: 6.1.0-beta.256
OS: Darwin arm64 25.5.0

For AI issues: which model did you use?

Sonnet 4.5

Does this stop you from using Cursor

No - Cursor works, but with this issue

Hi @Kenneth_Melvej!

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.