mcp-percona-pg
Related Servers
Alternatives to mcp-percona-pg
No user-submitted related servers found.
Related Servers
AlicenseNot gradedqualityBmaintenanceEnables AI agents to safely operate on PostgreSQL data through typed MCP tools with per-identity RBAC, guardrails, and immutable audit logging.1,070 npmMIT- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to safely query one or more PostgreSQL databases with read-only tools and explicitly approved write operations.63 npm1MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to interact with PostgreSQL databases through MCP, offering index tuning, query plan analysis, schema intelligence, health checks, and safe SQL execution, with support for multiple databases.1MIT
- AlicenseNot gradedqualityBmaintenanceSafe-write Postgres MCP server enabling secure read and write access to PostgreSQL databases with role-based separation and allowlist controls, allowing agents to query and modify data without risk of unrecoverable accidents.40 npmMIT
- FlicenseNot gradedqualityCmaintenanceEnables querying and modifying PostgreSQL databases through MCP tools with read/write operations, schema inspection, and write-safety constraints that limit modifications to the mcp schema.1-
- AlicenseNot gradedqualityCmaintenanceSafe, read-only-by-default Kubernetes access for AI agents via MCP. Provides explicit readonly, readwrite, and dangerous permission modes, plus MCPB bundles for desktop clients.2MIT
TDQS
Scored across 9 tools
get_cluster and get_cluster_status both describe cluster status and could be confused (summary vs full .status). list_clusters and list_contexts also overlap in listing clusters, though descriptions hint at a distinction. Other tools are clearly distinct.
All tools follow a consistent snake_case verb_noun pattern: list_* and get_*. No naming deviations or mixed conventions.
9 tools is well-scoped for a Kubernetes operator inspection server. Each tool maps to a distinct resource or config aspect, and nothing feels redundant by count.
The server is clearly read-only, but within that scope it lacks singular detail tools like get_backup or get_restore, and has no operations for cluster management (create/update/delete) or triggering backup/restore. Core inspection needs are covered, but notable gaps remain.