stream_query is what separates this from a plain query wrapper: batchSize and maxRows keep a wide table from arriving as a single payload. On the introspection side, list_indexes reports Vertica projections, which is the structure that actually governs performance in that engine. Whether execute_query can write is a configuration question rather than a property of the tool, so a read-only deployment is something you set up rather than something you are given.
A Vertica client covering query execution and schema introspection.
- SQL execution with bound parameters, under whatever query restrictions the deployment is configured with.
- Batched streaming of large result sets, with the batch size and a maximum row count in your hands.
- Tables and views in a schema with their metadata, and the definitions behind the views.
- A table's columns, data types and constraints, plus its projections with column and uniqueness information.
A reachable Vertica database and its connection settings; what a query is permitted to do depends on how the deployment is configured.
One command plus a key — claude mcp add vertica --scope user -- npx -y @hechtcarmel/vertica-mcp@latest --env-file /path/to/your/.env, then supply credentials