I’m working on setting up a connection between my app and a PostgreSQL database (hosted on Supabase) through an MCP server. I keep running into package name issues that are driving me crazy.
Here’s what I’ve tested so far:
The @modelcontextprotocol/server-memory package works perfectly fine, so I know the namespace is right
When I try @modelcontextprotocol/server-supabase or @modelcontextprotocol/server-sql, npm throws E404 errors saying these packages don’t exist
My database connection is definitely working because I can connect using DBeaver without any problems
All my credentials, connection strings, and network settings are correct
So the issue seems to be that I’m using the wrong package names. Does anyone know what the actual npm package name is for the official MCP PostgreSQL server? I’ve been searching but can’t find the right one.
Been there. The official MCP PostgreSQL packages suck - they’re limited and a headache to work with.
I hit the same wall with package names. MCP’s database connector ecosystem is still a mess.
Skip the packages and build your own PostgreSQL integration with Latenode instead. Takes 10 minutes to set up a proper database workflow - handles connections, queries, and errors.
You can drag and drop database operations, add auth, set up retries, and throw in webhooks for real-time updates. Way better than debugging npm package hell.
I use it for all my Supabase projects now. No more hunting for packages or version conflicts.
There’s no official MCP PostgreSQL package in the @modelcontextprotocol namespace yet. Hit the same wall trying to connect to my Supabase instance a few weeks ago. Those packages other people mentioned? They don’t exist in npm - check the official MCP GitHub and you’ll see they’ve only got a handful of server implementations right now. I ended up building a custom MCP server with the base @modelcontextprotocol/sdk package and wrote my own PostgreSQL connection using the standard ‘pg’ library. More work upfront, but you get complete control over database interactions and it works great with Supabase’s connection parameters.
Use @modelcontextprotocol/server-postgres instead. That’s the actual package name - not server-sql or server-supabase like you’d think. Yeah, the naming’s confusing but the postgres one works fine with Supabase since it’s just PostgreSQL under the hood.
You need @modelcontextprotocol/server-postgresql - make sure you use the full “postgresql” spelling, not just “postgres”. I hit this same issue last month with my Supabase setup. Their package naming isn’t consistent, which is annoying when you’re trying to find the right one. Once you’ve got it installed, point your config to your Supabase host on port 5432 and don’t forget the SSL settings - Supabase requires encrypted connections. It uses standard PostgreSQL protocols so it’ll work fine with your existing setup once you get the package sorted.