Skip to main content
Glama
hechtcarmel

Vertica MCP Server

by hechtcarmel

Related Servers

Alternatives to Vertica MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      C
      quality
      D
      maintenance
      Enables AI assistants to interact with Vertica Analytics Databases for querying, schema exploration, and performance optimization through natural language. It provides enterprise-grade features like fine-grained permissions, query streaming, and secure SSL/TLS connections.
      12
      13 PyPI
      4
      Apache 2.0
    • A
      license
      B
      quality
      D
      maintenance
      Enables interaction with Vertica databases through SQL queries, schema management, and bulk data operations. Supports connection pooling, SSL/TLS security, and configurable permissions for database operations.
      6
      Apache 2.0
    • A
      license
      A
      quality
      A
      maintenance
      Enables an AI assistant to query and browse multiple database engines read-only, with the ability to switch connections and engines dynamically during a session.
      18
      71 npm
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to query relational databases like MySQL, PostgreSQL, and Oracle using natural-language questions, dynamically discovering schemas and generating validated read-only SQL through configurable AI providers such as Groq, Claude, and Gemini.
      -
    • A
      license
      A
      quality
      D
      maintenance
      Enables AI assistants to interact with PostgreSQL databases using natural language queries, providing secure read-only access to database schemas and SQL translation capabilities.
      6
      9 npm
      ISC

    TDQS

    A4.1/5.0

    Scored across 6 tools

    Disambiguation4/5

    stream_query and execute_query both run SQL and could be confused, but their descriptions clearly separate bounded/subquery use from small-result or SHOW/DESCRIBE/EXPLAIN use. The four metadata tools have distinct purposes: tables, views, projections/indexes, and table column structure.

    Naming Consistency5/5

    All tool names follow a consistent snake_case verb_noun pattern: stream_query, execute_query, list_tables, list_views, list_indexes, get_table_structure. There are no mixed conventions or vague names.

    Tool Count5/5

    Six tools is a well-scoped set for a Vertica query and metadata server. Each tool has a clear role, and there are no redundant or filler tools.

    Completeness4/5

    The set covers query execution plus core metadata discovery for tables, views, projections, and table structures. Minor gaps remain, such as listing schemas or inspecting view column structure directly, but agents can generally work around these with SQL.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues