convez.ai
MCP ServerDados & AnalyticsIntermediário
Vidushi-8465

PostgreSQL MCP Server

Vidushi-8465/MCP-SERVER

Acesso read-only a PostgreSQL via Claude com 20 ferramentas de consulta

Ver no GitHub
InicialPluginScore · de 0 a 100

Servidor MCP que conecta Claude Desktop a bancos PostgreSQL com ferramentas read-only para descoberta de tabelas, buscas textuais, queries SELECT customizadas e suporte especializado para dados de Network Engineer (NE). Expõe 20 ferramentas organizadas em descoberta, acesso a dados, SQL customizado e ferramentas NE.

Instalação

$npx convez-ai Vidushi-8465/MCP-SERVER

1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.

Métricas

Estrelas
0
Forks
0
Acompanhando
0
Saúde
14%
Último commit
há 3 meses
Versão
—
Issues abertas
0
Contribuidores
3

Casos de uso

  • Explorar estrutura e dados de bancos PostgreSQL dentro do Claude Desktop
  • Executar queries SELECT e buscas textuais sem sair da conversa
  • Trabalhar com dados de Network Engineer (NE) com ferramentas especializadas
  • Análise e relatórios via SQL customizado através do Claude

Veredito

MCP bem estruturado para integração PostgreSQL read-only no Claude Desktop. Cobertura de 20 ferramentas é abrangente, com suporte específico para dados NE. Requer configuração inicial de credenciais e é adequado para exploração de dados e analytics sem risco de escrita.

README

A tradução para o português deste README ainda está na fila.

PostgreSQL MCP Server

Multi-table MCP server for Claude Desktop that connects to PostgreSQL and exposes read-only database tools for discovery, search, custom SELECT queries, and NE (Network Engineer) region data.

Quick start

  1. Install dependencies: pip install -r requirements.txt
  2. Copy .env.example to .env and fill in your DBeaver/PostgreSQL credentials
  3. Add the server to Claude Desktop config (see Claude Desktop setup)
  4. Restart Claude Desktop
  5. Ask Claude to run setup_all_tables and/or setup_ne_tables (or enable auto-setup in .env)

All 20 tools

Discovery & setup — general (6 tools)

ToolWhat it does
list_tablesLists all tables in the default schema
get_table_schemaShows columns, types, and primary key for any table
setup_all_tablesRegisters all tables and creates stored procedures
setup_tableRegisters a single table
list_registered_tablesShows which tables are ready to use
describe_databaseOverview of registered tables and procedures

Data access — any registered table (4 tools)

Pass table_name (use schema.table format when needed, e.g. public.ne_buildings):

ToolWhat it does
list_table_recordsPaginated list of rows
get_table_recordOne row by primary key
search_table_recordsText search across string columns
count_table_recordsTotal row count

Custom SQL (1 tool)

ToolWhat it does
execute_read_queryRun any SELECT query (joins, reports, analytics)

NE (Netwrok Engineer) data tools (9 tools)

For tables in the NE schema or whose names match the NE prefix (e.g. ne_buildings, ne_sites):

ToolWhat it does
setup_ne_tablesDiscover and register all NE tables with stored procedures
list_ne_tablesList discovered and registered NE tables
describe_ne_dataOverview of NE tables, columns, and procedures
ne_data_summaryRow counts across all NE tables
list_ne_recordsList rows from a specific NE table
get_ne_recordGet one NE record by primary key
search_ne_recordsSearch one NE table by text
search_all_ne_dataSearch across all NE tables at once
count_ne_recordsCount rows in one NE table

How NE tables are detected

A table is treated as NE data if any of these match:

  1. It lives in the schema set by NE_SCHEMA (e.g. ne)
  2. Its name starts with NE_TABLE_PREFIX (default: ne)
  3. Its name contains patterns like ne_, _ne, network_eng ineer, network_element

Configure in .env:

NE_SCHEMA=ne          # optional — dedicated NE schema
NE_TABLE_PREFIX=ne      # table name prefix in public schema
AUTO_SETUP_NE_TABLES=true

Database coverage

Works immediately (no setup required)

  • list_tables
  • get_table_schema
  • execute_read_query

Scope limits

LimitDetail
Default schemaDB_SCHEMA (default: public)
NE schemaOptional separate schema via NE_SCHEMA
RegistrationSome tables may fail setup (missing PK, type errors)
Procedureslist, count, search on all registered tables
Primary keyget_by_id requires a primary key

Summary

QuestionAnswer
How many tools?20 (11 general + 9 NE)
NE data supported?Yes — dedicated NE tools + auto-discovery
Same tools for every table?Yes — pass table_name or use NE tools
Works without setup?Only discovery + execute_read_query

Workflow in Claude

General data

  1. setup_all_tables → register everything
  2. describe_database → see what's ready
  3. list_table_records with table_name

NE data

  1. setup_ne_tables → register NE tables only
  2. describe_ne_data or ne_data_summary → overview
  3. list_ne_records, search_ne_records, or search_all_ne_data

Example prompts:

"Run setup_ne_tables and show me a summary of all NE data."

"Search all NE tables for 'Guwahati'."

"List 20 records from ne_buildings."

"Count rows in every NE table."


Setup

Install dependencies

cd c:\Vidushi\mcp-server
pip install -r requirements.txt

Environment variables (.env)

DB_HOST=your_host
DB_PORT=5432
DB_NAME=postgres
DB_USER=postgres
DB_PASSWORD=your_password
DB_SCHEMA=public
AUTO_SETUP_ALL_TABLES=true

# NE (Network Engineer) data
NE_SCHEMA=
NE_TABLE_PREFIX=ne
AUTO_SETUP_NE_TABLES=true
VariableDescription
DB_HOSTPostgreSQL host
DB_PORTPort (default: 5432)
DB_NAMEDatabase name
DB_USERUsername
DB_PASSWORDPassword
DB_SCHEMADefault schema (default: public)
AUTO_SETUP_ALL_TABLESRegister all tables on startup
NE_SCHEMAOptional dedicated schema for NE tables
NE_TABLE_PREFIXPrefix to match NE table names (default: ne)
AUTO_SETUP_NE_TABLESRegister NE tables on startup

Claude Desktop setup

Add to %APPDATA%\Claude\claude_desktop_config.json:

{
  "mcpServers": {
    "GIS MCP-Server": {
      "command": "python",
      "args": ["c:\\Vidushi\\mcp-server\\server.py"],
      "env": {
        "DB_HOST": "your_host",
        "DB_PORT": "5432",
        "DB_NAME": "postgres",
        "DB_USER": "postgres",
        "DB_PASSWORD": "your_password",
        "DB_SCHEMA": "public",
        "AUTO_SETUP_ALL_TABLES": "true",
        "NE_TABLE_PREFIX": "ne",
        "AUTO_SETUP_NE_TABLES": "true"
      }
    }
  }
}

Restart Claude Desktop after saving.

Logs

c:\Vidushi\mcp-server\logs\mcp-server.log

MCP uses stdio for protocol traffic. Logs go to the file only, not the console.


Project structure

mcp-server/
├── server.py           # MCP entry point and tool definitions
├── database.py         # PostgreSQL connection pool
├── config.py           # Environment configuration
├── logger.py           # File-based logging
├── procedures.py       # Stored procedure generation
├── table_registry.py   # Tracks registered tables
├── table_service.py    # Multi-table read logic
├── table_refs.py       # schema.table reference helpers
├── ne_service.py       # NE data discovery and operations
├── requirements.txt
├── .env
├── .env.example
├── readme.md
└── logs/

Run manually

python server.py
Ver o original no GitHub

Bom para

Relacionados