v0.2.0 "Waiting for server to respond to initialize request..."

[nsvrana]

Bug report

Describe the bug

Starting recently released version 0.2.0 causes it to timeout connecting:

2025-04-03 14:25:58.870 [info] Waiting for server to respond to initialize request...
2025-04-03 14:26:03.873 [info] Waiting for server to respond to initialize request...
2025-04-03 14:26:08.868 [info] Waiting for server to respond to initialize request...
2025-04-03 14:26:13.864 [info] Waiting for server to respond to initialize request...
2025-04-03 14:26:18.863 [info] Waiting for server to respond to initialize request...
2025-04-03 14:26:23.862 [info] Waiting for server to respond to initialize request...
2025-04-03 14:26:28.873 [info] Waiting for server to respond to initialize request...
2025-04-03 14:26:33.865 [info] Waiting for server to respond to initialize request...
2025-04-03 14:26:38.868 [info] Waiting for server to respond to initialize request...
2025-04-03 14:26:39.236 [info] Connection state: Error Process exited with code 1

Testing with 0.1.0 in the same environment works fine.

System information

• OS: Windows w/Ubuntu WSL
• MCP Client: Both VS Code and Claude
• Node version: v23.7.0

[gregnr]

Thanks for reporting @nsvrana. I tried to reproduce on macOS using both @latest and @0.2.0 explicitly, and both worked in Claude Desktop and Cursor. I wouldn't think that Windows would behave differently for this version specifically, but you never know.

Can you share the JSON config you are using (omitting your PAT)?

Thanks!

[nsvrana]

{
    "servers": {
        "supabase": {
            "command": "npx",
            "args": [
            "-y",
            "@supabase/mcp-server-supabase@latest",
            "--access-token",
            "token"
            ]
        }
    }
}

I also tried running it in MCP Inspector and it initially connects but when I go to list tools, I get the following:

Spawned stdio transport
Connected MCP client to backing server transport
Created web app transport
Created web app transport
Set up MCP proxy
Received message for sessionId 478b0098-8a7f-4e7f-b032-cfbd0bdd10ad
Error in /message route: Error: SSE connection not established
    at SSEServerTransport.handlePostMessage (file:///home/user/.npm/_npx/5a9d879542beca3a/node_modules/@modelcontextprotocol/sdk/dist/esm/server/sse.js:53:19)
    at file:///home/user/.npm/_npx/5a9d879542beca3a/node_modules/@modelcontextprotocol/inspector/server/build/index.js:130:25
    at Layer.handle [as handle_request] (/home/user/.npm/_npx/5a9d879542beca3a/node_modules/express/lib/router/layer.js:95:5)
    at next (/home/user/.npm/_npx/5a9d879542beca3a/node_modules/express/lib/router/route.js:149:13)
    at Route.dispatch (/home/user/.npm/_npx/5a9d879542beca3a/node_modules/express/lib/router/route.js:119:3)
    at Layer.handle [as handle_request] (/home/user/.npm/_npx/5a9d879542beca3a/node_modules/express/lib/router/layer.js:95:5)
    at /home/user/.npm/_npx/5a9d879542beca3a/node_modules/express/lib/router/index.js:284:15
    at Function.process_params (/home/user/.npm/_npx/5a9d879542beca3a/node_modules/express/lib/router/index.js:346:12)
    at next (/home/user/.npm/_npx/5a9d879542beca3a/node_modules/express/lib/router/index.js:280:10)
    at cors (/home/user/.npm/_npx/5a9d879542beca3a/node_modules/cors/lib/index.js:188:7)
node:_http_outgoing:699
    throw new ERR_HTTP_HEADERS_SENT('set');
          ^

Error [ERR_HTTP_HEADERS_SENT]: Cannot set headers after they are sent to the client
    at ServerResponse.setHeader (node:_http_outgoing:699:11)
    at ServerResponse.header (/home/user/.npm/_npx/5a9d879542beca3a/node_modules/express/lib/response.js:794:10)
    at ServerResponse.json (/home/user/.npm/_npx/5a9d879542beca3a/node_modules/express/lib/response.js:275:10)
    at file:///home/user/.npm/_npx/5a9d879542beca3a/node_modules/@modelcontextprotocol/inspector/server/build/index.js:134:25
    at process.processTicksAndRejections (node:internal/process/task_queues:105:5) {
  code: 'ERR_HTTP_HEADERS_SENT'
}

Node.js v23.7.0

[gregnr]

Since you mentioned you are using WSL on Windows, could you try using the "Windows (WSL)" config described in these docs:
https://supabase.com/docs/guides/getting-started/mcp

And let me know if that fixes anything?

[nsvrana]

That did not work, I receive Connection state: Error spawn wsl ENOENT since you cannot execute "wsl" from within the actual WSL environment.

I did just test running this in Windows itself by spawning the MCP Inspector inside of Powershell, then running the command, and it works fine. It appears to be something about the WSL environment (or maybe my specific WSL environment) that is causing it to fail.

[nsvrana]

I fixed it, although I'm not sure how you can fix it more broadly. I cloned the repo, and when I tried to build it, I received the following error:

~/supabase-mcp/packages/mcp-server-supabase$ npm install
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 @npmcli/[email protected]: This functionality has been moved to @npmcli/fs
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]: Rimraf versions prior to v4 are no longer supported
npm warn deprecated [email protected]: Rimraf versions prior to v4 are no longer supported
npm warn deprecated [email protected]: Rimraf versions prior to v4 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]: Glob versions prior to v9 are no longer supported
npm warn deprecated [email protected]: Glob versions prior to v9 are no longer supported
npm warn deprecated [email protected]: Glob versions prior to v9 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 error code 1
npm error path /home/user/supabase-mcp/node_modules/libpg-query
npm error command failed
npm error command sh -c node-pre-gyp install --fallback-to-build
npm error make: Entering directory '/home/user/supabase-mcp/node_modules/libpg-query/build'
npm error   CC(target) Release/obj.target/nothing/../node-addon-api/src/nothing.o
npm error rm -f Release/obj.target/../node-addon-api/src/nothing.a Release/obj.target/../node-addon-api/src/nothing.a.ar-file-list; mkdir -p `dirname Release/obj.target/../node-addon-api/src/nothing.a`
npm error ar crs Release/obj.target/../node-addon-api/src/nothing.a @Release/obj.target/../node-addon-api/src/nothing.a.ar-file-list
npm error   COPY Release/nothing.a
npm error   ACTION binding_gyp_queryparser_target_prebuild_dependencies libpg_query/include/pg_query.h
npm error make[1]: Entering directory '/tmp/tmp.sPWIWoQICa/libpg_query'
npm error compiling src/pg_query.c
npm error compiling src/pg_query_deparse.c
npm error compiling src/pg_query_fingerprint.c
npm error compiling src/pg_query_json_plpgsql.c
npm error compiling src/pg_query_normalize.c
npm error compiling src/pg_query_outfuncs_json.c
npm error compiling src/pg_query_outfuncs_protobuf.c
npm error compiling src/pg_query_parse.c
npm error compiling src/pg_query_parse_plpgsql.c
npm error compiling src/pg_query_readfuncs_protobuf.c
npm error Warning: protoc-gen-c not found, skipping protocol buffer regeneration
npm error compiling src/pg_query_scan.c
npm error compiling src/pg_query_split.c
npm error compiling src/postgres/src_backend_catalog_namespace.c
npm error compiling src/postgres/src_backend_catalog_pg_proc.c
npm error compiling src/postgres/src_backend_commands_define.c
npm error compiling src/postgres/src_backend_libpq_pqcomm.c
npm error compiling src/postgres/src_backend_nodes_bitmapset.c
npm error compiling src/postgres/src_backend_nodes_copyfuncs.c
npm error compiling src/postgres/src_backend_nodes_equalfuncs.c
npm error compiling src/postgres/src_backend_nodes_extensible.c
npm error compiling src/postgres/src_backend_nodes_list.c
npm error compiling src/postgres/src_backend_nodes_makefuncs.c
npm error compiling src/postgres/src_backend_nodes_nodeFuncs.c
npm error compiling src/postgres/src_backend_nodes_value.c
npm error compiling src/postgres/src_backend_parser_gram.c
npm error compiling src/postgres/src_backend_parser_parse_expr.c
npm error compiling src/postgres/src_backend_parser_parser.c
npm error compiling src/postgres/src_backend_parser_scan.c
npm error compiling src/postgres/src_backend_parser_scansup.c
npm error compiling src/postgres/src_backend_postmaster_postmaster.c
npm error compiling src/postgres/src_backend_storage_ipc_ipc.c
npm error compiling src/postgres/src_backend_storage_lmgr_s_lock.c
npm error compiling src/postgres/src_backend_tcop_postgres.c
npm error compiling src/postgres/src_backend_utils_adt_datum.c
npm error compiling src/postgres/src_backend_utils_adt_expandeddatum.c
npm error compiling src/postgres/src_backend_utils_adt_format_type.c
npm error compiling src/postgres/src_backend_utils_adt_ruleutils.c
npm error compiling src/postgres/src_backend_utils_error_assert.c
npm error compiling src/postgres/src_backend_utils_error_elog.c
npm error compiling src/postgres/src_backend_utils_fmgr_fmgr.c
npm error compiling src/postgres/src_backend_utils_hash_dynahash.c
npm error compiling src/postgres/src_backend_utils_init_globals.c
npm error compiling src/postgres/src_backend_utils_mb_mbutils.c
npm error compiling src/postgres/src_backend_utils_misc_guc.c
npm error compiling src/postgres/src_backend_utils_mmgr_aset.c
npm error compiling src/postgres/src_backend_utils_mmgr_mcxt.c
npm error compiling src/postgres/src_common_encnames.c
npm error compiling src/postgres/src_common_hashfn.c
npm error compiling src/postgres/src_common_keywords.c
npm error compiling src/postgres/src_common_kwlookup.c
npm error compiling src/postgres/src_common_psprintf.c
npm error compiling src/postgres/src_common_string.c
npm error compiling src/postgres/src_common_stringinfo.c
npm error compiling src/postgres/src_common_wchar.c
npm error compiling src/postgres/src_pl_plpgsql_src_pl_comp.c
npm error compiling src/postgres/src_pl_plpgsql_src_pl_funcs.c
npm error compiling src/postgres/src_pl_plpgsql_src_pl_gram.c
npm error compiling src/postgres/src_pl_plpgsql_src_pl_handler.c
npm error compiling src/postgres/src_pl_plpgsql_src_pl_scanner.c
npm error compiling src/postgres/src_port_erand48.c
npm error compiling src/postgres/src_port_pg_bitutils.c
npm error compiling src/postgres/src_port_pgsleep.c
npm error compiling src/postgres/src_port_pgstrcasecmp.c
npm error compiling src/postgres/src_port_qsort.c
npm error compiling src/postgres/src_port_random.c
npm error compiling src/postgres/src_port_snprintf.c
npm error make[1]: Leaving directory '/tmp/tmp.sPWIWoQICa/libpg_query'
npm error ERROR: 'make' command failed
npm error make: Leaving directory '/home/user/supabase-mcp/node_modules/libpg-query/build'
npm error Failed to execute '/home/user/.nvm/versions/node/v23.7.0/bin/node /home/user/.nvm/versions/node/v23.7.0/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js build --fallback-to-build --module=/home/user/supabase-mcp/node_modules/libpg-query/build/Release/queryparser.node --module_name=queryparser --module_path=/home/user/supabase-mcp/node_modules/libpg-query/build/Release --napi_version=10 --node_abi_napi=napi --napi_build_version=0 --node_napi_label=node-v131' (1)
npm error node-pre-gyp info it worked if it ends with ok
npm error node-pre-gyp info using [email protected]
npm error node-pre-gyp info using [email protected] | linux | x64
npm error node-pre-gyp info check checked for "/home/user/supabase-mcp/node_modules/libpg-query/build/Release/queryparser.node" (not found)
npm error node-pre-gyp http GET https://supabase-public-artifacts-bucket.s3.amazonaws.com/libpg-query-node/queryparser-v13.3.2-node-v131-linux-x64.tar.gz
npm error node-pre-gyp ERR! install response status 404 Not Found on https://supabase-public-artifacts-bucket.s3.amazonaws.com/libpg-query-node/queryparser-v13.3.2-node-v131-linux-x64.tar.gz
npm error node-pre-gyp WARN Pre-built binaries not installable for [email protected] and [email protected] (node-v131 ABI, glibc) (falling back to source compile with node-gyp)
npm error node-pre-gyp WARN Hit error response status 404 Not Found on https://supabase-public-artifacts-bucket.s3.amazonaws.com/libpg-query-node/queryparser-v13.3.2-node-v131-linux-x64.tar.gz
npm error gyp info it worked if it ends with ok
npm error gyp info using [email protected]
npm error gyp info using [email protected] | linux | x64
npm error gyp info ok
npm error gyp info it worked if it ends with ok
npm error gyp info using [email protected]
npm error gyp info using [email protected] | linux | x64
npm error gyp info find Python using Python version 3.12.3 found at "/usr/bin/python3"
npm error gyp info spawn /usr/bin/python3
npm error gyp info spawn args [
npm error gyp info spawn args '/home/user/.nvm/versions/node/v23.7.0/lib/node_modules/npm/node_modules/node-gyp/gyp/gyp_main.py',
npm error gyp info spawn args 'binding.gyp',
npm error gyp info spawn args '-f',
npm error gyp info spawn args 'make',
npm error gyp info spawn args '-I',
npm error gyp info spawn args '/home/user/supabase-mcp/node_modules/libpg-query/build/config.gypi',
npm error gyp info spawn args '-I',
npm error gyp info spawn args '/home/user/.nvm/versions/node/v23.7.0/lib/node_modules/npm/node_modules/node-gyp/addon.gypi',
npm error gyp info spawn args '-I',
npm error gyp info spawn args '/home/user/.cache/node-gyp/23.7.0/include/node/common.gypi',
npm error gyp info spawn args '-Dlibrary=shared_library',
npm error gyp info spawn args '-Dvisibility=default',
npm error gyp info spawn args '-Dnode_root_dir=/home/user/.cache/node-gyp/23.7.0',
npm error gyp info spawn args '-Dnode_gyp_dir=/home/user/.nvm/versions/node/v23.7.0/lib/node_modules/npm/node_modules/node-gyp',
npm error gyp info spawn args '-Dnode_lib_file=/home/user/.cache/node-gyp/23.7.0/<(target_arch)/node.lib',
npm error gyp info spawn args '-Dmodule_root_dir=/home/user/supabase-mcp/node_modules/libpg-query',
npm error gyp info spawn args '-Dnode_engine=v8',
npm error gyp info spawn args '--depth=.',
npm error gyp info spawn args '--no-parallel',
npm error gyp info spawn args '--generator-output',
npm error gyp info spawn args 'build',
npm error gyp info spawn args '-Goutput_dir=.'
npm error gyp info spawn args ]
npm error gyp info ok
npm error gyp info it worked if it ends with ok
npm error gyp info using [email protected]
npm error gyp info using [email protected] | linux | x64
npm error gyp info spawn make
npm error gyp info spawn args [ 'BUILDTYPE=Release', '-C', 'build' ]
npm error Cloning into 'libpg_query'...
npm error Note: switching to 'e7c14fe399c4903223362790c212bcbeb6832864'.
npm error
npm error You are in 'detached HEAD' state. You can look around, make experimental
npm error changes and commit them, and you can discard any commits you make in this
npm error state without impacting any branches by switching back to a branch.
npm error
npm error If you want to create a new branch to retain commits you create, you may
npm error do so (now or later) by using -c with the switch command. Example:
npm error
npm error   git switch -c <new-branch-name>
npm error
npm error Or undo this operation with:
npm error
npm error   git switch -
npm error
npm error Turn off this advice by setting config variable advice.detachedHead to false
npm error
npm error HEAD is now at e7c14fe fix(makefile): ar var to inherit ar command
npm error src/postgres/src_port_snprintf.c:374:1: error: conflicting types for ‘strchrnul’; have ‘const char *(const char *, int)’
npm error   374 | strchrnul(const char *s, int c)
npm error       | ^~~~~~~~~
npm error In file included from ./src/postgres/include/c.h:61,
npm error                  from src/postgres/src_port_snprintf.c:62:
npm error /usr/include/string.h:286:14: note: previous declaration of ‘strchrnul’ with type ‘char *(const char *, int)’
npm error   286 | extern char *strchrnul (const char *__s, int __c)
npm error       |              ^~~~~~~~~
npm error make[1]: *** [Makefile:172: src/postgres/src_port_snprintf.o] Error 1
npm error make: *** [queryparser.target.mk:13: libpg_query/include/pg_query.h] Error 1
npm error gyp ERR! build error
npm error gyp ERR! stack Error: `make` failed with exit code: 2
npm error gyp ERR! stack at ChildProcess.<anonymous> (/home/user/.nvm/versions/node/v23.7.0/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:216:23)
npm error gyp ERR! System Linux 5.15.167.4-microsoft-standard-WSL2
npm error gyp ERR! command "/home/user/.nvm/versions/node/v23.7.0/bin/node" "/home/user/.nvm/versions/node/v23.7.0/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "build" "--fallback-to-build" "--module=/home/user/supabase-mcp/node_modules/libpg-query/build/Release/queryparser.node" "--module_name=queryparser" "--module_path=/home/user/supabase-mcp/node_modules/libpg-query/build/Release" "--napi_version=10" "--node_abi_napi=napi" "--napi_build_version=0" "--node_napi_label=node-v131"
npm error gyp ERR! cwd /home/user/supabase-mcp/node_modules/libpg-query
npm error gyp ERR! node -v v23.7.0
npm error gyp ERR! node-gyp -v v11.0.0
npm error gyp ERR! not ok
npm error node-pre-gyp ERR! build error
npm error node-pre-gyp ERR! stack Error: Failed to execute '/home/user/.nvm/versions/node/v23.7.0/bin/node /home/user/.nvm/versions/node/v23.7.0/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js build --fallback-to-build --module=/home/user/supabase-mcp/node_modules/libpg-query/build/Release/queryparser.node --module_name=queryparser --module_path=/home/user/supabase-mcp/node_modules/libpg-query/build/Release --napi_version=10 --node_abi_napi=napi --napi_build_version=0 --node_napi_label=node-v131' (1)
npm error node-pre-gyp ERR! stack     at ChildProcess.<anonymous> (/home/user/supabase-mcp/node_modules/@mapbox/node-pre-gyp/lib/util/compile.js:89:23)
npm error node-pre-gyp ERR! stack     at ChildProcess.emit (node:events:507:28)
npm error node-pre-gyp ERR! stack     at maybeClose (node:internal/child_process:1101:16)
npm error node-pre-gyp ERR! stack     at ChildProcess._handle.onexit (node:internal/child_process:305:5)
npm error node-pre-gyp ERR! System Linux 5.15.167.4-microsoft-standard-WSL2
npm error node-pre-gyp ERR! command "/home/user/.nvm/versions/node/v23.7.0/bin/node" "/home/user/supabase-mcp/node_modules/.bin/node-pre-gyp" "install" "--fallback-to-build"
npm error node-pre-gyp ERR! cwd /home/user/supabase-mcp/node_modules/libpg-query
npm error node-pre-gyp ERR! node -v v23.7.0
npm error node-pre-gyp ERR! node-pre-gyp -v v1.0.11
npm error node-pre-gyp ERR! not ok

I searched for node-gyp builds fail on WSL and found my way to this issue: nodejs/node-gyp#1207

So I ran npm install -g node-gyp make, then retried the build and it worked. I went back over to VS Code and the MCP server spun up and worked as expected.

[c4mz]

Also getting this on Mac using github copilot in VSCode.

2025-04-04 13:10:11.443 [info] Connection state: Starting
2025-04-04 13:10:11.443 [info] Connection state: Running
2025-04-04 13:10:15.298 [warning] [server stderr] npm warn deprecated @npmcli/[email protected]: This functionality has been moved to @npmcli/fs
2025-04-04 13:10:15.299 [warning] [server stderr] 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.
2025-04-04 13:10:15.308 [warning] [server stderr] npm warn deprecated [email protected]: This package is no longer supported.
2025-04-04 13:10:15.323 [warning] [server stderr] npm warn deprecated [email protected]: This package is no longer supported.
2025-04-04 13:10:15.331 [warning] [server stderr] npm warn deprecated [email protected]: Rimraf versions prior to v4 are no longer supported
2025-04-04 13:10:15.342 [warning] [server stderr] npm warn deprecated [email protected]: This package is no longer supported.
2025-04-04 13:10:15.346 [warning] [server stderr] npm warn deprecated [email protected]: This package is no longer supported.
2025-04-04 13:10:15.349 [warning] [server stderr] npm warn deprecated [email protected]: Glob versions prior to v9 are no longer supported
2025-04-04 13:10:15.406 [warning] [server stderr] npm warn deprecated [email protected]: This package is no longer supported.
2025-04-04 13:10:15.415 [warning] [server stderr] npm warn deprecated [email protected]: This package is no longer supported.
2025-04-04 13:10:16.444 [info] Waiting for server to respond to initialize request...
2025-04-04 13:10:21.445 [info] Waiting for server to respond to initialize request...
2025-04-04 13:10:26.445 [info] Waiting for server to respond to initialize request...
2025-04-04 13:10:31.444 [info] Waiting for server to respond to initialize request...
2025-04-04 13:10:36.444 [info] Waiting for server to respond to initialize request...
2025-04-04 13:10:41.445 [info] Waiting for server to respond to initialize request...
2025-04-04 13:10:45.176 [info] Connection state: Error Process exited with code 1
2025-04-04 13:10:56.349 [info] Stopping server supabase

[gregnr]

@c4mz did the server work for you pre-0.2.0 and only start failing at 0.2.0 too? If not let's open a new issue so that we can track these separately (please include your Node version too as I've noticed some folks have had issues with older versions).

[gregnr]

@nsvrana Ah yup, prefixing the command with wsl assumes you are running it from outside of WSL (eg. within VS Code on Windows). If your MCP client is also within WSL (like the inspector), you would follow the Linux instructions (no prefix).

I'd like to understand what the underlying issue was for you so that this doesn't reoccur for others. To confirm, you never got 0.2.0 working within WSL, but it does work natively on Windows? And within WSL, you were only able to get it to work by cloning and building this repo yourself?

[c4mz]

@c4mz did the server work for you pre-0.2.0 and only start failing at 0.2.0 too? If not let's open a new issue so that we can track these separately (please include your Node version too as I've noticed some folks have had issues with older versions).

Using node 23.10.0 This is my first time using the mcp so didn't use it before latest.

[izidorome]

After several attempts, I managed to resolve the issue by following these steps:

1. Remove the npx cache:

   rm -rf ~/.npm/npx

   This changed the error message, indicating that stale cache data was a contributing factor.

2. Clear the npm cache completely:

   npm cache clean --force

   This ensured that any potentially corrupted cache was removed.

3. Restart Claude Desktop (or Cursor):
   A full restart of the application was necessary to apply the changes.

Environment

Node version: v22.8.0
npm version: 10.8.2

[nsvrana]

@gregnr - I uninstalled the package that I built from source and deleted the NPX cache, then re-ran and it still worked.

It seems npm install -g node-gyp make fixed it globally.

[rerouted]

Ok confirmed that @nsvrana command above resolved my issue. Windsurf now reports the server green with 22 tools available. 🙌

Mac OSX
Node: v23.9.0
npm: 11.2.0

[VincentMartin24]

sucess to connect the '22' tools but then still not working but finally working with cline but this is kind of "buggy" but it seems to works now

i finally sucess doing this steps so i get the 22 tools

MACOS, VSCODE INSIDER, copilot and ( node.20 )

[thubv]

same error

[christophemenager]

Same error on Macos + vscode copilot MCP servers

2025-04-07 09:34:40.395 [info] Starting server Supabase
2025-04-07 09:34:40.395 [info] Connection state: Starting
2025-04-07 09:34:40.395 [info] Starting server from LocalProcess extension host
2025-04-07 09:34:40.396 [info] Connection state: Starting
2025-04-07 09:34:40.397 [info] Connection state: Running
2025-04-07 09:34:45.400 [info] Waiting for server to respond to `initialize` request...
2025-04-07 09:34:48.469 [warning] [server stderr] 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.
2025-04-07 09:34:48.484 [warning] [server stderr] npm WARN deprecated [email protected]: Glob versions prior to v9 are no longer supported
2025-04-07 09:34:48.641 [warning] [server stderr] npm WARN deprecated [email protected]: This package is no longer supported.
2025-04-07 09:34:48.643 [warning] [server stderr] npm WARN deprecated [email protected]: This package is no longer supported.
2025-04-07 09:34:48.702 [warning] [server stderr] npm WARN deprecated @npmcli/[email protected]: This functionality has been moved to @npmcli/fs
2025-04-07 09:34:48.754 [warning] [server stderr] npm WARN deprecated [email protected]: This package is no longer supported.
2025-04-07 09:34:48.754 [warning] [server stderr] npm WARN deprecated [email protected]: Rimraf versions prior to v4 are no longer supported
2025-04-07 09:34:49.246 [warning] [server stderr] npm WARN deprecated [email protected]: This package is no longer supported.
2025-04-07 09:34:49.247 [warning] [server stderr] npm WARN deprecated [email protected]: This package is no longer supported.
2025-04-07 09:34:49.249 [warning] [server stderr] npm WARN deprecated [email protected]: This package is no longer supported.
2025-04-07 09:34:50.398 [info] Waiting for server to respond to `initialize` request...
2025-04-07 09:34:55.399 [info] Waiting for server to respond to `initialize` request...
2025-04-07 09:35:00.401 [info] Waiting for server to respond to `initialize` request...
2025-04-07 09:35:04.784 [info] Connection state: Error Process exited with code 1