Unable to run multiple instances of @modelcontextprotocol/server-postgres simultaneously

[jeffmylife]

Describe the bug
It's not possible to run multiple instances of @modelcontextprotocol/server-postgres simultaneously to connect to different databases (e.g., production and development).

When doing this, the chat always chooses the first one specified in order of mcp.json.

I presume it's an mcp problem since cursor's agent can see both of the servers, it just cannot run the development no matter what i say!

To Reproduce
Steps to reproduce the behavior:

1. Set up two database connections in your MCP configuration

{
  "mcpServers": {
    "Production Database": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-postgres",
        "postgresql://postgres:password@production-db.example.com:5432/postgres"
      ]
    },
    "Development Database": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-postgres",
        "postgresql://postgres:password@localhost:54322/postgres"
      ]
    }
  }
}

2. Try to get the chat model to call the second (development one in this case) and it will just always show production data.

Expected behavior
It should be possible to run multiple instances of the server simultaneously, each connecting to a different database, without conflicts or interference.

Or, it should error if there are two.

Additional context
I was doing this in cursor with local and remote supabase databases.

[jarodtaylor]

Same issue. I was hoping to find a solve in here!

[olaservo]

Thanks for reporting this. This server has been moved to the archived repository at https://github.com/modelcontextprotocol/servers-archived to reduce maintenance overhead, so we can focus our efforts on a smaller set of core servers.
Since this server is no longer actively maintained, we recommend checking out the alternatives listed in the Readme.