pg-db-operation-mcp-server

An MCP server package intended to expose PostgreSQL database operations to an AI agent (pg “db operation” tooling) via the Model Context Protocol (MCP).

Evaluated Apr 04, 2026 (27d ago)
Homepage ↗ Infrastructure postgres mcp database sql agent-integration
⚙ Agent Friendliness
32
/ 100
Can an agent use this?
🔒 Security
34
/ 100
Is it safe for agents?
⚡ Reliability
22
/ 100
Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality
45
Documentation
30
Error Messages
0
Auth Simplicity
45
Rate Limits
0

🔒 Security

TLS Enforcement
40
Auth Strength
40
Scope Granularity
20
Dep. Hygiene
40
Secret Handling
30

Because no repository/README content was provided, scores reflect uncertainty. For Postgres-integrating MCP servers, the main risks are overly-broad DB credentials, execution of arbitrary/destructive SQL, insufficient auditing, lack of TLS enforcement between MCP server and Postgres, and missing guardrails (query allowlists/parameterization).

⚡ Reliability

Uptime/SLA
0
Version Stability
30
Breaking Changes
30
Error Recovery
30
AF Security Reliability

Use Cases

  • Allow an LLM/agent to run controlled SQL/DB operations against PostgreSQL using MCP tool calls
  • Build agent workflows that need read/write access to Postgres data (e.g., reporting, CRUD assistance, data backfills)
  • Integrate Postgres operations into an agent platform that supports MCP

Not For

  • Untrusted agents performing arbitrary SQL without safety controls
  • Publicly exposed database access from the internet without network protections
  • Highly compliance-sensitive environments without explicit auditing, least-privilege DB credentials, and query allowlists

Interface

REST API
No
GraphQL
No
gRPC
No
MCP Server
Yes
SDK
No
Webhooks
No

Authentication

Methods: PostgreSQL credentials (implied for DB access)
OAuth: No Scopes: No

No README/package details were provided here about MCP-server authentication (e.g., whether the MCP server itself requires an API key). Auth appears likely to rely on database credentials, but this cannot be confirmed from the provided data.

Pricing

Free tier: No
Requires CC: No

No pricing information provided; likely self-hosted/open-source MCP server.

Agent Metadata

Pagination
none
Idempotent
False
Retry Guidance
Not documented

Known Gotchas

  • Agent-generated SQL can be destructive unless guarded (allowlists, read-only roles, transaction boundaries).
  • Without parameterization and strict input handling, the agent may produce unsafe queries.
  • If the MCP server exposes “execute SQL” style tools, agents may attempt multi-statement batches that are unsafe or unsupported.
  • DB connection errors/timeouts may require retry/backoff; guidance may not be documented.

Alternatives

Full Evaluation Report

Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for pg-db-operation-mcp-server.

AI-powered analysis · PDF + markdown · Delivered within 30 minutes

$99

Package Brief

Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.

Delivered within 10 minutes

$3

Score Monitoring

Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.

Continuous monitoring

$3/mo

Scores are editorial opinions as of 2026-04-04.

8642
Packages Evaluated
17761
Need Evaluation
586
Need Re-evaluation
Community Powered