Vertica MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| VERTICA_SSL | No | Enable SSL connection | false |
| VERTICA_HOST | Yes | Database hostname | |
| VERTICA_PORT | No | Database port | 5433 |
| VERTICA_USER | Yes | Username | |
| VERTICA_DATABASE | Yes | Database name | |
| VERTICA_PASSWORD | No | Password (optional) | |
| VERTICA_QUERY_TIMEOUT | No | Query timeout in milliseconds | 60000 |
| VERTICA_READONLY_MODE | No | Enable readonly mode (only SELECT/SHOW/DESCRIBE/EXPLAIN/WITH queries allowed) | true |
| VERTICA_DEFAULT_SCHEMA | No | Default database schema | public |
| VERTICA_CONNECTION_LIMIT | No | Connection pool limit (max: 100) | 10 |
| VERTICA_SSL_REJECT_UNAUTHORIZED | No | Reject unauthorized SSL certificates | true |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| execute_queryA | Run one SQL statement for small results or SHOW/DESCRIBE/EXPLAIN. Read-only statement checks and transactions are enabled. Results have no row cap; add LIMIT or use stream_query. Database functions can have side effects. |
| stream_queryA | Use for bounded SELECT/WITH results valid inside a subquery. Executes once and returns batches in one response; no cursor or incremental streaming. Use ORDER BY for reproducible ordering. Functions can have side effects. |
| list_tablesA | Discover visible tables in one schema before querying. Returns all matching metadata without pagination; does not read table data. |
| list_viewsA | Discover views and their SQL in one schema. Returns all visible matches without pagination; definition is a 200-character preview and fullDefinition is complete. |
| list_indexesA | Inspect one table's Vertica projections and column sort positions. Returns all projection-column catalog rows without pagination. isUnique reflects key-constraint projection status, not a uniqueness proof. |
| get_table_structureA | Inspect one existing table's columns, nullability, constraints and owner before composing SQL. Does not read table data. Fails if the table is absent or invisible; does not inspect views. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
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.
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.
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.
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.