PostgreSQL MCP Server
Vidushi-8465/MCP-SERVER
Acesso read-only a PostgreSQL via Claude com 20 ferramentas de consulta
Ver no GitHubServidor 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-SERVER1 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
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
- Install dependencies:
pip install -r requirements.txt - Copy
.env.exampleto.envand fill in your DBeaver/PostgreSQL credentials - Add the server to Claude Desktop config (see Claude Desktop setup)
- Restart Claude Desktop
- Ask Claude to run
setup_all_tablesand/orsetup_ne_tables(or enable auto-setup in.env)
All 20 tools
Discovery & setup — general (6 tools)
| Tool | What it does |
|---|---|
list_tables | Lists all tables in the default schema |
get_table_schema | Shows columns, types, and primary key for any table |
setup_all_tables | Registers all tables and creates stored procedures |
setup_table | Registers a single table |
list_registered_tables | Shows which tables are ready to use |
describe_database | Overview 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):
| Tool | What it does |
|---|---|
list_table_records | Paginated list of rows |
get_table_record | One row by primary key |
search_table_records | Text search across string columns |
count_table_records | Total row count |
Custom SQL (1 tool)
| Tool | What it does |
|---|---|
execute_read_query | Run 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):
| Tool | What it does |
|---|---|
setup_ne_tables | Discover and register all NE tables with stored procedures |
list_ne_tables | List discovered and registered NE tables |
describe_ne_data | Overview of NE tables, columns, and procedures |
ne_data_summary | Row counts across all NE tables |
list_ne_records | List rows from a specific NE table |
get_ne_record | Get one NE record by primary key |
search_ne_records | Search one NE table by text |
search_all_ne_data | Search across all NE tables at once |
count_ne_records | Count rows in one NE table |
How NE tables are detected
A table is treated as NE data if any of these match:
- It lives in the schema set by
NE_SCHEMA(e.g.ne) - Its name starts with
NE_TABLE_PREFIX(default:ne) - 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_tablesget_table_schemaexecute_read_query
Scope limits
| Limit | Detail |
|---|---|
| Default schema | DB_SCHEMA (default: public) |
| NE schema | Optional separate schema via NE_SCHEMA |
| Registration | Some tables may fail setup (missing PK, type errors) |
| Procedures | list, count, search on all registered tables |
| Primary key | get_by_id requires a primary key |
Summary
| Question | Answer |
|---|---|
| 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
setup_all_tables→ register everythingdescribe_database→ see what's readylist_table_recordswithtable_name
NE data
setup_ne_tables→ register NE tables onlydescribe_ne_dataorne_data_summary→ overviewlist_ne_records,search_ne_records, orsearch_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
| Variable | Description |
|---|---|
DB_HOST | PostgreSQL host |
DB_PORT | Port (default: 5432) |
DB_NAME | Database name |
DB_USER | Username |
DB_PASSWORD | Password |
DB_SCHEMA | Default schema (default: public) |
AUTO_SETUP_ALL_TABLES | Register all tables on startup |
NE_SCHEMA | Optional dedicated schema for NE tables |
NE_TABLE_PREFIX | Prefix to match NE table names (default: ne) |
AUTO_SETUP_NE_TABLES | Register 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