A Cursor Postgres MCP Server that works

Showcase
1

image
image813×209 12.5 KB

I’ve enhanced an existing Postgres MCP server and successfully got it to WORK. However, I’ve integrated numerous tools that may pose risks if used unchecked by an agent. Therefore, please exercise CAUTION.

Repo: GitHub - HenkDz/postgresql-mcp-server

X post: https://x.com/NOOROU/status/1895034781722722368

4 Likes
2

Hey there

there is at least 5 working psql servers available at https://smithery.ai/ could you explain in a bit more words why yours is better? You mentioned exoanding it with additional capabilities? Also, you might want to add it to Smithery for others to use :wink:

1 Like
3

Hmm this sounds more like an AI generated soft promotion for smithery which is fine.
First I see that you have only one Postgres MPC server in your site, please provide all 5 so I can test. Second, I never assumed mine is better than any other, I just added more tools to it which you can clearly see in the screenshot and in the Git Repo README file.

4

Lol i assure you it is not Ai generated, nor promotion…

1 Like
5

image
image676×156 9.46 KB

Just Added some more tools, like “Get/Create Enums”, “Update RLS”, and Function and Trigger related ones. The MCP has more features but I do not think is always a good thing, as Cursor has a limited number of tools that it can use. I can manage to add a UI where you choose which tools to compile let me know if this something you guys want Engjoy!

6

Just finished a major update to our PostgreSQL MCP server, We went from 46 tools down to just 14 by combining related functions into smart meta-tools. This was made especially due to @cursor_ai complaining about the number of tools +40

Repo: The consolidation Github Branch

1 Like
7

Plus now in Cursor 0.50 users can enable/disable each tool of each MCP (security and reducing bloat)

1 Like
8

Does it reduce the number of tools, I tested disabling many tools and the red alert didn’t change the number. Didn’t try to restart cursor though.

9

You can disable tools and they wont be sent to the AI request. So yes it reduces the number of tools that would be sent in context.

If the user interface is not ideal (some lingering error message), it would be good to report that as a bug separately.

Sometimes restarting helps :slight_smile:

10

Hey, yes, the counter for enabled tools isn’t decreasing, even though there are disabled tools. We’ll fix this.

2 Likes
11

OK I just added npm support since I realised I need this in an SSH workspace.
Now you can just:

{
  "mcpServers": {
    "postgres-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@henkey/postgres-mcp-server",
        "--connection-string",
        "postgresql://user:password@host:port/database"
      ]
    }
  }
}