Skip to content

Conversation

mattrossman
Copy link
Contributor

@mattrossman mattrossman commented Sep 3, 2025

Exports the package version from package.json as a version constant so other apps can more easily read this at runtime:

import { version } from "@supabase/mcp-server-supabase"

console.log(version) // Prints "0.5.1"

Adds a test that this constant is exported.

Also includes README updates:

  • Specifies active LTS of Node.js as a prerequisite: crypto is not defined #53
  • Updates "For developers" section to reflect pnpm instructions and MCP config for local development

I think the --ignore-scripts flag suggested in #75 is no longer needed (maybe a difference in behavior with pnpm #127). I'm able to just pnpm install on latest MacOS without issue so I've removed that callout.

Ref AI-141

@gregnr gregnr merged commit c4f4252 into main Sep 3, 2025
2 checks passed
@renierbleeker83
Copy link

@mattrossman, I've tried your suggestions but still running into the same issue "crypto not defined". The weird thing is, a few weeks back I had the issue for a while, then it "magically" worked again and now running into it again.

Here's a report of Claude of all the actions we've tried and the mcp log file. Would be amazing if you can help me out. (Ps im not a developer)

supabase-mcp-bug-report.log
mcp-server-supabase-lifedashboard.log

@mattrossman
Copy link
Contributor Author

Hey @renierbleeker83, looking at that mcp-server-supabase-lifedashboard.log file, your client appears to be using Node 18.20.8 instead of the recommended Active LTS version:

2025-09-09T19:06:33.048Z [supabase-lifedashboard] [info] Using MCP server command: /Users/renierbleeker/.nvm/versions/node/v18.20.8/bin/npx

Since you're using nvm you may need to experiment with your config (like specifying an absolute path to npx instead of relying on PATH resolution) to make sure it's using the appropriate version of npx, as there's several versions installed:

  paths: [
    '/Users/renierbleeker/.nvm/versions/node/v18.20.8/bin',
    '/Users/renierbleeker/.nvm/versions/node/v20.19.4/bin',
    '/Users/renierbleeker/.nvm/versions/node/v20.19.5/bin',
    '/Users/renierbleeker/.nvm/versions/node/v22.14.0/bin',
    ...
 ]

If you have further difficulties, let's continue the discussion in a more relevant thread such as #53

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants