pg-metadata-mcp-server

Provides an MCP (Model Context Protocol) server for accessing/inspecting pg-metadata (PostgreSQL metadata). It is intended to let AI agents query database metadata via MCP tools rather than direct DB connections.

Evaluated Apr 04, 2026 (17d ago)
Homepage ↗ DevTools mcp postgres database-metadata schema-introspection ai-agents
⚙ Agent Friendliness
33
/ 100
Can an agent use this?
🔒 Security
32
/ 100
Is it safe for agents?
⚡ Reliability
26
/ 100
Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

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

🔒 Security

TLS Enforcement
50
Auth Strength
25
Scope Granularity
10
Dep. Hygiene
50
Secret Handling
30

Without provided implementation details, TLS/auth/secret handling cannot be confirmed. MCP servers that connect to Postgres typically require careful handling of DB credentials and principle-of-least-privilege DB roles; ensure the tool does not expose sensitive metadata beyond necessity.

⚡ Reliability

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

Best When

You want an LLM/agent workflow to fetch Postgres metadata on-demand through MCP tool calls.

Avoid When

You require strong guarantees about rate limits, auth, and structured error contracts that are not documented by the package.

Use Cases

  • • AI agents that need to understand database schema/relations (tables, columns, types)
  • • Generating SQL or migration plans using up-to-date Postgres metadata
  • • Building admin/debug tooling for Postgres environments via agent-driven metadata lookup

Not For

  • • Writing/committing database changes (DDL/DML) unless explicitly provided as separate tools
  • • Handling production traffic workloads with strict uptime/SLA requirements (unless documented)
  • • Environments where outbound network access to the MCP server is not allowed

Interface

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

Authentication

Methods: unknown
OAuth: No Scopes: No

No auth details were provided in the supplied information, so auth method and scope granularity cannot be confirmed.

Pricing

Free tier: No
Requires CC: No

Agent Metadata

Pagination
none
Idempotent
False
Retry Guidance
Not documented

Known Gotchas

  • ⚠ MCP tool behaviors (timeouts, pagination, and error formats) may be undocumented or inconsistent across implementations
  • ⚠ Agents may assume DB schema completeness; metadata can be stale depending on connection/role/permissions
  • ⚠ Metadata queries can be slow on large catalogs without caching/limits

Alternatives

Direct Postgres access via a DB driver/ORM + schema introspection dbt/Schema export tools (schema.yml generation) Other MCP servers focused on database schema introspection (if available)

Full Evaluation Report

Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for pg-metadata-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
API endpoint ↗ Agent guide ↗ Report inaccuracy

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

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