PostgreSQL Database Manager MCP server for AI agents

The PostgreSQL MCP Server provides Model Context Protocol capabilities for managing PostgreSQL databases. It assists with database analysis, setup instructions, and debugging to help users optimize their PostgreSQL implementations.

Features Overview

Database Analysis

The server can analyze your PostgreSQL database configuration and performance:

// Example usage
{
  "connectionString": "postgresql://user:password@localhost:5432/dbname",
  "analysisType": "performance" // Optional: "configuration" | "performance" | "security"
}

Setup Instructions

Get step-by-step guidance for installing and configuring PostgreSQL:

// Example usage
{
  "platform": "linux", // Required: "linux" | "macos" | "windows"
  "version": "15", // Optional: PostgreSQL version
  "useCase": "production" // Optional: "development" | "production"
}

Database Debugging

Troubleshoot common PostgreSQL issues:

// Example usage
{
  "connectionString": "postgresql://user:password@localhost:5432/dbname",
  "issue": "performance", // Required: "connection" | "performance" | "locks" | "replication"
  "logLevel": "debug" // Optional: "info" | "debug" | "trace"
}

Prerequisites

Before installation, ensure you have:

Node.js >= 18.0.0
PostgreSQL server (for target database operations)
Network access to target PostgreSQL instances

Installation Options

Automated Installation via Smithery

The easiest way to install PostgreSQL MCP Server for Claude Desktop is through Smithery:

npx -y @smithery/cli install @nahmanmate/postgresql-mcp-server --client claude

Manual Installation

For manual installation, follow these steps:

Clone the repository
Install dependencies:
```
npm install
```
Build the server:
```
npm run build
```

Add the server to your MCP settings file:

{
  "mcpServers": {
    "postgresql-mcp": {
      "command": "node",
      "args": ["/path/to/postgresql-mcp-server/build/index.js"],
      "disabled": false,
      "alwaysAllow": []
    }
  }
}

Security Best Practices

When using the PostgreSQL MCP Server, follow these security recommendations:

Always use secure connection strings with proper credentials
Follow production security recommendations for sensitive environments
Regularly monitor and analyze database performance
Keep PostgreSQL version up to date
Implement proper backup strategies
Use connection pooling for better resource management
Implement proper error handling and logging
Conduct regular security audits and updates

Error Handling

The server handles various error scenarios:

Connection failures
Query timeouts
Authentication errors
Permission issues
Resource constraints

How to add this MCP server to Cursor

There are two ways to add an MCP server to Cursor. The most common way is to add the server globally in the ~/.cursor/mcp.json file so that it is available in all of your projects.

If you only need the server in a single project, you can add it to the project instead by creating or adding it to the .cursor/mcp.json file.

Adding an MCP server to Cursor globally

To add a global MCP server go to Cursor Settings > MCP and click "Add new global MCP server".

When you click that button the ~/.cursor/mcp.json file will be opened and you can add your server like this:

{
    "mcpServers": {
        "cursor-rules-mcp": {
            "command": "npx",
            "args": [
                "-y",
                "cursor-rules-mcp"
            ]
        }
    }
}

Adding an MCP server to a project

To add an MCP server to a project you can create a new .cursor/mcp.json file or add it to the existing one. This will look exactly the same as the global MCP server example above.

How to use the MCP server

Once the server is installed, you might need to head back to Settings > MCP and click the refresh button.

The Cursor agent will then be able to see the available tools the added MCP server has available and will call them when it needs to.

You can also explictly ask the agent to use the tool by mentioning the tool name and describing what the function does.