1. Conduid
  2. Data
  3. Psql MCP Go
MCP server · Data

Psql MCP Go

PostgrSQL MCP server

Unclaimed last commit a year ago data
41Fair

Scored 5 months ago · breakdown

About Psql MCP Go

Psql MCP Go is an MCP server published by vladmsnk in the Data category: postgrSQL MCP server.

Six months or more without a commit doesn't mean the server is broken, but check the open issues before depending on it in production.

Install

From source
git clone https://github.com/vladmsnk/psql-mcp-go

This server has no ConduID identity, so agent calls to it are not receipted. Pin the version you install and review the source before granting it credentials.

Ask AI

✦

Ask AI about Psql MCP Go

Powered by Claude · Grounded in docs

I know everything about Psql MCP Go. Ask me about installation, configuration, usage, or troubleshooting.

Security checks

  • ✓README presentThe repository ships documentation.
  • !Scoped permissionsDoesn't declare a permission scope. Assume it can do anything its process can.

4 checks have not been run yet.

README

PostgreSQL MCP Server

A Model Context Protocol (MCP) server that provides tools and prompts for PostgreSQL database monitoring and optimization.

Features

  • Connection statistics and monitoring
  • Database size information
  • Index usage statistics
  • Slow query detection
  • Cache hit ratio monitoring
  • Table statistics
  • Table analysis tools
  • Query EXPLAIN plan generation

Installation

go get github.com/yourusername/psql-go-mcp

Configuration

The server requires PostgreSQL connection details to be provided via environment variables:

export PG_HOST=localhost
export PG_PORT=5432
export PG_USER=postgres
export PG_PASSWORD=postgres
export PG_DB=postgres
export PG_SSLMODE=disable

Usage

Starting the Server

psql-go-mcp

Available Tools

  1. postgresql/connection-stats: Get PostgreSQL connection statistics
  2. postgresql/database-size: Get PostgreSQL database size information
  3. postgresql/index-usage: Get PostgreSQL index usage statistics
  4. postgresql/slow-queries: Get PostgreSQL slow query statistics
  5. postgresql/cache-hit-ratio: Get PostgreSQL cache hit ratio
  6. postgresql/table-stats: Get PostgreSQL table statistics
  7. postgresql/analyze-table: Analyze a specific PostgreSQL table
  8. postgresql/explain-query: Get the EXPLAIN plan for a PostgreSQL query

Available Prompts

  1. connection-optimization: Guidance on optimizing PostgreSQL connections
  2. query-optimization: Guidance on optimizing PostgreSQL queries

Using with MCP Inspector

The MCP Inspector provides a visual interface for interacting with the PostgreSQL MCP server. Here's how to use it:

  1. Install the MCP Inspector:

    npm install -g @modelcontextprotocol/inspector
    
  2. Create Inspector Configuration: Create a file named inspector-config.json with the following content:

    {
      "mcpServers": {
        "my-server": {
          "type": "sse",
          "url": "http://localhost:8080/events"
        }
      }
    }
    
  3. Start the Inspector:

    npx @modelcontextprotocol/inspector --config inspector-config.json --server my-server
    
  4. Access the Inspector UI:

    • Open your browser and navigate to http://127.0.0.1:6274
    • You should see the Inspector interface with your PostgreSQL MCP server connected
    • Use the interface to:
      • View available tools and prompts
      • Execute database monitoring tools
      • Get optimization guidance
      • Monitor real-time database statistics

Requirements

README copy captured when this server was indexed; it may lag the repository. The original is authoritative.

Questions

About Psql MCP Go

How do I install Psql MCP Go?

No package has been published for this server, so install it from source: clone the repository and follow its README.

Is Psql MCP Go safe to use with an AI agent?

Its trust score is 41 out of 100 (fair). It passes 1 of the 2 static security checks run so far; the failures are listed above. It has no ConduID identity yet, so agent calls to it are not receipted.

Is Psql MCP Go still maintained?

The last commit was a year ago. That's long enough that you should check whether the maintainer is responding to issues before depending on it.