Skip to main content
Glama

Related Servers

Alternatives to run402-mcp

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      C
      maintenance
      A secure PostgreSQL MCP server allowing AI models to read, write, update, and delete database records with parameterized queries, transactional dry-runs, disposable testing, and automated backups.
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables connecting Postgres databases to MCP clients with built-in query and inspection tools, custom parametrized SQL tools, scoped API keys, group permissions, and audit logging.
      5
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to securely interact with PostgreSQL databases through a standardized MCP interface, supporting SQL queries, schema inspection, and database management.
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables governed access to corporate Postgres databases via MCP, supporting read-only queries, confirmed data and schema changes, query explanation, audit trail retrieval, and role-based policies with optional Vault secret integration.
      10
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      An extensible MCP server for database operations that supports PostgreSQL for managing schemas, tables, data, and user permissions. It features automatic migration recording for DDL changes and integrates with various AI-powered editors like Cursor, Zed, and Claude Code.
      27 npm
      2
      MIT

    TDQS

    A3.9/5.0

    Scored across 8 tools

    Disambiguation4/5

    The main overlaps are `up` vs `deploy` and `whoami` vs `status`, but descriptions explicitly clarify their boundaries: `up` handles setup plus deploy, `deploy` only deploys, `whoami` covers remote identity, and `status` covers local wallet/org state. `docs` and `run` are related but distinct, and `expand_result`/`doctor` are clearly separate, leaving only minor room for confusion.

    Naming Consistency3/5

    Names are mostly lowercase CLI-style tokens (`up`, `whoami`, `deploy`, `status`, `docs`, `doctor`, `run`), but they mix verbs, nouns, and an adverb, and `expand_result` uses snake_case while the rest are single words. There is no predictable verb_noun pattern across the set.

    Tool Count5/5

    Eight tools is well-scoped for a deployment/control-plane MCP: core workflows, identity/state inspection, diagnostics, documentation, result expansion, and a generic SDK escape hatch each have a clear role. Nothing feels redundant or missing at the count level.

    Completeness4/5

    The universal `run` tool provides broad SDK coverage, and `up`, `deploy`, `whoami`, `status`, and `doctor` cover the main lifecycle paths. However, direct secret-management operations and some one-time-secret flows are unavailable or require CLI fallback, which is a minor but real gap.

    Maintenance

    ActivityActive
    ResponsivenessResponsive