Skip to main content
Glama
dockndevai

mcp-percona-pg

Related Servers

Alternatives to mcp-percona-pg

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to safely operate on PostgreSQL data through typed MCP tools with per-identity RBAC, guardrails, and immutable audit logging.
      1,070 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients to safely query one or more PostgreSQL databases with read-only tools and explicitly approved write operations.
      63 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables 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.
      1
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Safe-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 npm
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables 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
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      Safe, 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.
      2
      MIT

    TDQS

    A3.6/5.0

    Scored across 9 tools

    Disambiguation3/5

    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.

    Naming Consistency5/5

    All tools follow a consistent snake_case verb_noun pattern: list_* and get_*. No naming deviations or mixed conventions.

    Tool Count5/5

    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.

    Completeness3/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive