Skip to content
Agentmart
Submit a tool

DBeast PostgreSQL MCP

PostgreSQL MCP server for schema, query, health, security, and performance analysis.

Connector by snss10 · GitHub account verified by the MCP Registry

IndexedMITLocal (stdio)★ 9
Write a review

Install

Works with Claude Code, Codex, VS Code, Cursor, Windsurf, Claude Desktop. Read the repository before you give any tool access to your data.

npx agentmarket install connector/snss10-dbeast

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

PostgreSQL MCP server for schema, query, health, security, and performance analysis.

Reviews

Write a review

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this server can do and what it asks for, from its tool list and install config. Checked Oct 25, 2026.

Tools
15 read · 1 write · 0 delete · 5 not yet classified
Secrets
3 (API keys, tokens or passwords)
Install scripts
Not scanned yet
Runs as
Docker image

Tools by what they do 21

Read from the source code; the running server may list different tools.

Read 15 · Look things up without changing anything.

  • analyze_impact
  • analyze_query
  • configuration_review
  • database_health
  • duplicate_detection
  • execute_query
  • get_audit_logs
  • get_schema
  • health_check
  • list_audit_files
  • query_optimizer
  • query_performance
Show 3 more tools
  • replication_status
  • security_audit
  • sensitive_data_scan

Write 1 · Create, change, send or run things.

  • disconnect

Not yet classified 5 · We could not tell from the name and description.

  • connect
  • data_quality_report
  • dependency_analysis
  • maintenance_analysis
  • partition_analysis

Secrets and settings it asks for

Secrets: values you paste in that let it act as you.

  • AWS_SECRET_NAME
  • DATABASE_URL
  • DB_PASSWORD

Other settings (environment variables or headers).

  • AWS_REGION
  • DB_HOST
  • DB_NAME
  • DB_PORT
  • DB_USER

Tools (21)

Read from the source code; the running server may differ. Descriptions are the server’s own words; hidden characters are shown as [U+…].

  • analyze_impact

    Preview DELETE/UPDATE/DROP impact WITHOUT executing. Shows affected rows and rollback SQL. LEVEL: Query (write operation preview - never executes) USE FOR: previewing write impact, cascade effects, risk assessment. DO NOT USE FOR: reading data (execute_query), INSERT operations. Examples: analyze_impact(query="DELETE FROM users WHERE status='inactive'", schema='public') analyze_impact(query="UPDATE orders SET status='cancelled' WHERE id=1", schema='shipment')

  • analyze_query

    Validate SQL syntax, detect anti-patterns, N+1, duplicates. LEVEL: Query (SQL statement analysis - no DB connection needed for basic parsing) USE FOR: SQL validation, N+1 detection, batch analysis. DO NOT USE FOR: running queries (execute_query), write impact (analyze_impact). Examples: analyze_query(query='SELECT * FROM users') analyze_query(query='SELECT * FROM users', schema='shipment', include_explain=True)

  • configuration_review

    Reviews PostgreSQL configuration settings and provides tuning observations. LEVEL: Server (PostgreSQL instance configuration) USE FOR: configuration, settings, postgresql.conf, parameters, tuning, memory, extensions, "why is DB slow globally?", "is autovacuum configured correctly?", server tuning review. DO NOT USE FOR: database-level health (use database_health), query optimization (use query_optimizer), replication settings (use replication_status), table-specific issues (use maintenance_analysis). INCLUDE OPTIONS: - 'all': Everything (default) - 'memory': shared_buffers, effective_ca…

  • connect

    Connect to PostgreSQL or check connection status. LEVEL: Server (connection management) USE FOR: connecting, checking status, discovering databases. DO NOT USE FOR: health metrics (database_health), queries (execute_query). ERROR RECOVERY: - "connection refused": Check host/port, ensure PostgreSQL is running - "authentication failed": Verify user/password credentials - "database does not exist": List available databases with discover=True - "SSL required": Add use_ssl=True or check server SSL config - "certificate verify failed": Set ssl_verify=False for SSH tunnels Examples: connect()…

  • data_quality_report

    Comprehensive data quality analysis - nulls, types, empty tables, outliers, soft deletes. LEVEL: Database ↔ Schema ↔ Table ↔ Column (multi-level tool) - schema='all': Database level - quality analysis for ALL schemas - schema='<name>': Schema level - all tables in that schema (supports ANY schema name: 'sales', 'billing', 'auth', 'analytics', etc.) - table='users': Table level - specific table analysis - outlier_column='age': Column level - outlier detection for specific column REQUIRED: Specify schema explicitly - use 'all' for all schemas or a specific schema name. USE FOR: da…

  • database_health

    Live database health - monitors active connections, sessions, locks, transactions. LEVEL: Database (single database monitoring) USE FOR: "is database healthy?", connection issues, lock problems, blocked queries, idle transactions, deadlock detection, XID wraparound check, "why is DB slow right now?". DO NOT USE FOR: index analysis (use maintenance_analysis), slow query history (use query_performance), table sizes/stats (use maintenance_analysis), query optimization (use query_optimizer), PostgreSQL server config (use configuration_review), replication (use replication_status). REAL-TIME: Sho…

  • dependency_analysis

    Comprehensive dependency analysis - views, functions, triggers, sequences, FDW. LEVEL: Database ↔ Schema ↔ Table (multi-level tool) - schema='all': Database level - dependencies for ALL schemas - schema='<name>': Schema level - dependencies in that schema (supports ANY schema name: 'sales', 'billing', 'auth', 'analytics', etc.) - table='users': Table level - what depends on this specific table REQUIRED: Specify schema explicitly - use 'all' for all schemas or a specific schema name. USE FOR: dependencies, views, functions, triggers, sequences, extensions, FDW, lineage, "what depen…

  • disconnect

    Close the database connection and release pool resources. LEVEL: Server (connection management) USE FOR: ending session, cleanup, releasing connections. DO NOT USE FOR: checking status (use connect() or health_check).

  • duplicate_detection

    Detect duplicate rows in a table based on specified columns. LEVEL: Table ↔ Column (requires table and columns parameters) USE FOR: finding duplicates, duplicate rows, "are there duplicate emails?", detecting duplicate records, data deduplication analysis. DO NOT USE FOR: general data quality (use data_quality_report), schema structure (use get_schema), null analysis (use data_quality_report with include='nulls'). Examples: duplicate_detection(table='users', columns='email', schema='public') duplicate_detection(table='orders', columns='customer_id,product_id', schema='shipment')

  • execute_query

    Execute read-only SELECT queries. Writes are blocked. LEVEL: Data (actual table data retrieval) USE FOR: fetching data, counting rows, aggregations, joins. DO NOT USE FOR: INSERT/UPDATE/DELETE (use analyze_impact first). ERROR RECOVERY: - "relation does not exist": Verify table name with get_schema() - "permission denied": User lacks SELECT privilege on table - "query timeout": Reduce limit, add WHERE clause, or increase timeout_ms - "not connected": Call connect() first Examples: execute_query(query='SELECT * FROM users LIMIT 10') execute_query(query='SELECT COUNT(*) FROM orders')

  • get_audit_logs

    Retrieve MCP audit logs for accountability and debugging. USE FOR: viewing tool call history, debugging issues, compliance audits. Examples: get_audit_logs() - Today's logs get_audit_logs(date='2026-05-29') - Specific date get_audit_logs(limit=10) - Last 10 entries

  • get_schema

    Discover database schema - tables, columns, relationships, indexes. LEVEL: Database (lists all schemas) or Schema (specific schema details) USE FOR: listing tables, columns, foreign keys, ERD generation. DO NOT USE FOR: table data (execute_query), index health (maintenance_analysis). ERROR RECOVERY: - "schema not found": Call get_schema() without params to list all schemas - "no tables found": Schema exists but is empty, verify with execute_query - "not connected": Call connect() first or pass url parameter PAGINATION: For large schemas (100+ tables), use limit/offset. Examples: get_s…

  • health_check

    Check connection health - pool stats, version, extensions. LEVEL: Server (connection management) USE FOR: connection status, pool health, "is database reachable?". DO NOT USE FOR: database metrics (database_health), query stats (query_performance).

  • list_audit_files

    List available audit log files. USE FOR: finding available log dates, checking log sizes. Returns list of log files with date, size, and entry count.

  • maintenance_analysis

    Table and index maintenance - analyzes indexes, vacuum status, table bloat, FK indexes. LEVEL: Database ↔ Schema ↔ Table (multi-level tool) - schema='all': Database level - maintenance status for ALL schemas - schema='<name>': Schema level - all tables in that schema (supports ANY schema name: 'sales', 'billing', 'auth', 'analytics', etc.) - table='users': Table level - specific table analysis REQUIRED: Specify schema explicitly - use 'all' for all schemas or a specific schema name. USE FOR: finding unused indexes, duplicate indexes, tables needing vacuum, FK missing indexes, tabl…

Show 6 more tools
  • partition_analysis

    Partition analysis - list all partitioned tables or analyze specific table. LEVEL: Schema ↔ Table (multi-level tool) - table=None (default): Lists all partitioned tables across ALL schemas - table='orders': Requires schema - detailed partition analysis for that table USE FOR: partitions, partition analysis, partition details, partition size, inheritance, "which tables are partitioned?", partition skew detection, empty partition identification. DO NOT USE FOR: non-partitioned table maintenance (use maintenance_analysis), schema structure (use get_schema), index health (use maintenance_ana…

  • query_optimizer

    Optimize slow queries - EXPLAIN plan, table stats, index recommendations. LEVEL: Query (single query optimization) USE FOR: slow query diagnosis, CREATE INDEX suggestions, execution plans. DO NOT USE FOR: running queries (execute_query), syntax validation (analyze_query). Examples: query_optimizer(query='SELECT * FROM orders WHERE customer_id=123', schema='shipment') query_optimizer(query='SELECT * FROM users', schema='public', run_explain=True)

  • query_performance

    Historical query stats - shows top queries by time/calls/IO from pg_stat_statements. LEVEL: Database (database-wide query statistics) USE FOR: "what queries are slowest?", finding high-frequency queries, cache hit analysis, queries using temp files, overall query patterns, "which queries consume most time?". DO NOT USE FOR: analyzing ONE specific query (use query_optimizer), live running queries (use database_health), index recommendations (use maintenance_analysis), query syntax validation (use analyze_query). REQUIRES: pg_stat_statements extension installed. Examples: query_performanc…

  • replication_status

    Comprehensive replication health - physical, logical, CDC, slots, WAL, archiving. LEVEL: Server (PostgreSQL instance level) USE FOR: replication status, replica lag, standby, streaming replication, replication slots, CDC, logical replication, publications, subscriptions, WAL archiving, backup progress, "is replication healthy?", "how far behind is the replica?". DO NOT USE FOR: database-level health (use database_health), query performance (use query_performance), PostgreSQL settings (use configuration_review). INCLUDE OPTIONS: - 'all': Everything (default) - 'physical': Standbys, strea…

  • security_audit

    Audit roles, privileges, RLS, SSL, and security definer functions. LEVEL: Schema or Database (schema='all') REQUIRED: Specify schema explicitly - use 'all' for all schemas or a specific schema name. USE FOR: security audit, role permissions, RLS policies, SSL status. DO NOT USE FOR: PII detection (sensitive_data_scan), data quality. INCLUDE: all, roles, privileges, rls, ssl, sensitive, functions Examples: security_audit(schema='sales') - Audit sales schema security_audit(schema='all') - All schemas security_audit(schema='billing', include='roles') - Roles only in billing

  • sensitive_data_scan

    Find PII/PHI columns - passwords, credit cards, SSN, emails. LEVEL: Database (scans all schemas by default) or Schema (if specified) USE FOR: finding sensitive data, GDPR compliance, security review. DO NOT USE FOR: permissions (security_audit), data quality (data_quality_report). Examples: sensitive_data_scan() - Scan all schemas sensitive_data_scan(schema='public') - Public schema only

Signals

Stars
9
Forks
0
Open issues
0
Last commit
Jun 10, 2026 (4 months ago)
Last release
Jun 10, 2026 (4 months ago)

From GitHub (fetched Oct 24, 2026).

Details

Registry name
io.github.snss10/dbeast
Version
2.0.2
Auth
API key
Packages
oci ghcr.io/snss10/dbeast:2.0.2
License
MIT
Repository
github.com/snss10/DBeast
First seen
Oct 24, 2026
Last checked
Oct 24, 2026
Source
Official MCP Registrygithub-graphql
Cite this page

DBeast PostgreSQL MCP. Agent Mart. https://agentmart.dev/connectors/snss10-dbeast (last updated 2026-10-24)