MCP.Market

Postgres AIops MCP server

by AIops-tools·io.github.AIops-tools/postgres-aiops·v0.13.0

Governed PostgreSQL DBA ops: slow-query RCA, bloat/vacuum & blocking-lock analysis; 35 MCP tools.

A91/100grade A
What users say
No reviews yet
Be the first
Safety scan
A91/100

not scanned yet

Adoption
Growing

0 stars135 downloads/wk

Reviews

Write one

Nobody has reviewed Postgres AIops yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Postgres AIops tools

No tool declarations could be read from the package source. They show once the server is installed.

Not scanned yet. New listings are scanned within a day or two of arriving.

How Postgres AIops compares

Against every graded Databases MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
91/100
higher than 85% of 802 Databases servers
Downloads a week
135
more than 65% of 328 Databases servers with a package

Release history: 3 versions in the registry since 2026-09-15, latest 2026-10-30, typically one every 30 days.

Install Postgres AIops in Claude Code, Cursor or VS Code

claude mcp add postgres-aiops -- uvx postgres-aiops
Add to Cursor

What the publisher says

From the Postgres AIops repository's README, as published. We do not edit it. Read it on GitHub

<!-- mcp-name: io.github.AIops-tools/postgres-aiops -->

Postgres AIops

Disclaimer: Community-maintained open-source project. Not affiliated with, endorsed by, or sponsored by the PostgreSQL Global Development Group or any vendor. "PostgreSQL" and the elephant logo are trademarks of the PostgreSQL Community Association; all product/trademark names belong to their respective owners. MIT licensed.

Governed AI-ops for PostgreSQL DBA operations — connecting to a server with psycopg 3 and reading the system catalogs and pgstat views — with a built-in governance harness: unified audit log, token/runaway budget guard, undo-token recording, and descriptive risk-tier labels. Beyond the mock test suite, the reads, a governed write, and its undo have been exercised against a live PostgreSQL 16.14 instance — see docs/VERIFICATION.md.

What it does

Three flagship signature analyses, plus the guarded reads and writes around them:

EXPLAIN plan) and map its numbers — mean time, cache-hit ratio, temp spill, call count, plan node types — to a cited cause and a concrete action. Every finding carries its measured number, not a black-box verdict.

  • Slow-query RCA — take the worst pgstatstatements entry (plus an optional

recency into a ranked, cited recommendation (VACUUM / tune autovacuum).

  • Bloat & vacuum analysis — combine per-table dead-tuple ratio and autovacuum

name the root blocker (blocks others, waits on none), and give the action; a cycle is flagged as a likely deadlock.

  • Blocking lock-chain RCA — build the wait-for tree from pgblockingpids,

What works

  • CLI (postgres-aiops ...): init, overview, server, activity, query, index, table, repl, analyze, remediate, secret, doctor, mcp.
  • MCP server (postgres-aiops mcp or postgres-aiops-mcp): 35 tools (25 read, 10 write), every one wrapped with the bundled @governed_tool harness.
  • Encrypted credentials: the role password lives in an encrypted store ~/.postgres-aiops/secrets.enc (Fernet + scrypt) — never plaintext on disk. Unlock with a master password from POSTGRESAIOPSMASTER_PASSWORD (MCP/CI) or an interactive prompt (CLI).
  • Reversibility: mutating writes fetch the real before-state first and record a faithful inverse — createindex↔dropindex; dropindex captures pggetindexdef so undo recreates it exactly; updatesetting captures the prior value so undo sets it back. Irreversible ops (terminatebackend, cancelquery, runvacuum, runanalyze, reindex, resetquerystats) record prior stats for audit but declare no undo.
  • Safety: every state-changing CLI op supports --dry-run and requires double confirmation; every write MCP tool takes a dry_run preview. All identifiers that cannot be parameterised (table/index/GUC names) are validated and quoted; all values are bound query parameters.

Capability matrix (35 MCP tools)

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Postgres AIops: common questions

Is Postgres AIops MCP server safe?
Yes, by our scan: it is graded A (91/100). Read the Postgres AIops safety report
How do I install Postgres AIops?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Postgres AIops need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Postgres AIops maintained?
The last commit was 49 days ago (2026-09-16). The latest release is v0.13.0.
What can I use instead of Postgres AIops?
Servers from other publishers that do the same job: PostgreSQL MCP server, PostgreSQL MCP Server and Postgres MCP server. Compare all Postgres AIops alternatives.
How does Postgres AIops compare with other Databases MCP servers?
safety score 91/100 (higher than 85% of 802 Databases servers); downloads a week 135 (more than 65% of 328 Databases servers with a package). Full comparison.

Alternatives to Postgres AIops

Same job from other publishers: the closest match first, then the best rated.

All Postgres AIops alternatives →
  • PostgreSQL
    MCP server for PostgreSQL: local, Docker, RDS, Neon, Supabase, or behind an SSH bastion.
    B
  • PostgreSQL MCP Server
    PostgreSQL MCP server - query, schema introspection, explain, and health checks for AI assistants
    B
  • Postgres
    Enterprise PostgreSQL MCP server with NL queries, hybrid search (pgvector+BM25), and web UI
    A
  • PostgreSQL MCP Server
    PostgreSQL MCP server with 203 tools, connection pooling, HTTP/SSE, OAuth 2.1, and tool filtering
    A
  • DBHub
    Token-efficient database MCP server for PostgreSQL, MySQL, MariaDB, SQL Server, Oracle, SQLite
    A

More from AIops-tools →