supabase-community
Claude Desktop (and npx in general on windows 10)
Can't get the supabase mcp working.
I've tried two different machines, with different node versions using nvm and without.
I have vs code with c++ compilers installed, ran ~3h of troubleshooting with Claude, tried everything.
Claude Desktop mcp spinup log:
2025-04-05T12:10:27.870Z [supabase] [info] Initializing server... 2025-04-05T12:10:27.917Z [supabase] [info] Server started and connected successfully 2025-04-05T12:10:27.919Z [supabase] [info] Message from client: {"method":"initialize","params":{"protocolVersion":"2024-11-05","capabilities":{},"clientInfo":{"name":"claude-ai","version":"0.1.0"}},"jsonrpc":"2.0","id":0} npm warn deprecated @npmcli/[email protected]: This functionality has been moved to @npmcli/fs npm warn deprecated [email protected]: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful. npm warn deprecated [email protected]: This package is no longer supported. npm warn deprecated [email protected]: This package is no longer supported. npm warn deprecated [email protected]: This package is no longer supported. npm warn deprecated [email protected]: Rimraf versions prior to v4 are no longer supported npm warn deprecated [email protected]: Glob versions prior to v9 are no longer supported npm warn deprecated [email protected]: This package is no longer supported. npm warn deprecated [email protected]: This package is no longer supported. npm warn deprecated [email protected]: This package is no longer supported. npm warn cleanup Failed to remove some directories [ npm warn cleanup [ npm warn cleanup '\\\\?\\C:\\Users\\phili\\AppData\\Local\\npm-cache\\_npx\\53c4795544aaa350\\node_modules', npm warn cleanup [Error: EPERM: operation not permitted, rmdir 'C:\Users\phili\AppData\Local\npm-cache\_npx\53c4795544aaa350\node_modules\@modelcontextprotocol\sdk\dist\cjs\server\auth'] { npm warn cleanup errno: -4048, npm warn cleanup code: 'EPERM', npm warn cleanup syscall: 'rmdir', npm warn cleanup path: 'C:\\Users\\phili\\AppData\\Local\\npm-cache\\_npx\\53c4795544aaa350\\node_modules\\@modelcontextprotocol\\sdk\\dist\\cjs\\server\\auth' npm warn cleanup } npm warn cleanup ], npm warn cleanup [ npm warn cleanup '\\\\?\\C:\\Users\\phili\\AppData\\Local\\npm-cache\\_npx\\53c4795544aaa350\\node_modules\\pino-abstract-transport', npm warn cleanup [Error: EPERM: operation not permitted, rmdir 'C:\Users\phili\AppData\Local\npm-cache\_npx\53c4795544aaa350\node_modules\pino-abstract-transport\node_modules'] { npm warn cleanup errno: -4048, npm warn cleanup code: 'EPERM', npm warn cleanup syscall: 'rmdir', npm warn cleanup path: 'C:\\Users\\phili\\AppData\\Local\\npm-cache\\_npx\\53c4795544aaa350\\node_modules\\pino-abstract-transport\\node_modules' npm warn cleanup } npm warn cleanup ] npm warn cleanup ] 2025-04-05T12:11:13.438Z [supabase] [info] Server transport closed 2025-04-05T12:11:13.438Z [supabase] [info] Client transport closed 2025-04-05T12:11:13.439Z [supabase] [info] Server transport closed unexpectedly, this is likely due to the process exiting early. If you are developing this MCP server you can add output to stderr (i.e. console.error('...')in JavaScript,print('...', file=sys.stderr)in python) and it will appear in this log. 2025-04-05T12:11:13.439Z [supabase] [error] Server disconnected. For troubleshooting guidance, please visit our [debugging documentation](https://modelcontextprotocol.io/docs/tools/debugging) {"context":"connection"} 2025-04-05T12:11:13.439Z [supabase] [info] Client transport closed
truncated npm log:
1865 warn deprecated @npmcli/[email protected]: This functionality has been moved to @npmcli/fs 1866 warn deprecated [email protected]: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful. 1867 warn deprecated [email protected]: This package is no longer supported. 1868 warn deprecated [email protected]: This package is no longer supported. 1869 warn deprecated [email protected]: Rimraf versions prior to v4 are no longer supported 1870 warn deprecated [email protected]: Glob versions prior to v9 are no longer supported 1871 warn deprecated [email protected]: This package is no longer supported. 1872 warn deprecated [email protected]: This package is no longer supported. 1873 warn deprecated [email protected]: This package is no longer supported. 1874 warn deprecated [email protected]: This package is no longer supported. 1875 info run [email protected] install node_modules/libpg-query node-pre-gyp install --fallback-to-build 1876 info run [email protected] install { code: 1, signal: null } 1877 silly unfinished npm timer reify 1743855182388 1878 silly unfinished npm timer reify:build 1743855187508 1879 silly unfinished npm timer build 1743855187509 1880 silly unfinished npm timer build:deps 1743855187509 1881 silly unfinished npm timer build:run:install 1743855187597 1882 silly unfinished npm timer build:run:install:node_modules/libpg-query 1743855187597 1883 verbose cwd C:\temp\mpc_supabase_fix 1884 verbose os Windows_NT 10.0.19045 1885 verbose node v23.11.0 1886 verbose npm v10.9.2 1887 verbose exit 1 1888 verbose code 1
Can't get it to work properly,... any ideas? Seems to be related to libpg-query. I've tried different versions and it seems like the @latest i can install with npm install libpg-query@latest without an error, but the version used in the project not. Not sure how to fix this
Thanks for reporting @FlipEngineering. We've identified a Windows-specific issue in #43 that sounds related. Once that's merged I'll let you know and we can see if that fixes this for you.
Hey @FlipEngineering, the Windows issues has been resolved - would you mind trying again with the latest version?
Hey @FlipEngineering, another user indicated the libpg-query issue is resolved by the PR https://github.com/supabase-community/supabase-mcp/pull/43#issuecomment-2788289507 so I'm closing this issue for now. If it persists for you we can reopen to investigate further.
