Vertica MCP Server

A Model Context Protocol (MCP) server for Vertica databases. Enables AI assistants to query and explore Vertica databases through natural language.

Safety-first design: Readonly mode by default. Write operations require explicit configuration.

Features

• 6 MCP Tools: Query execution, streaming, schema discovery
• Readonly Protection: Only SELECT/SHOW/DESCRIBE/EXPLAIN/WITH queries by default
• Large Dataset Streaming: Efficient batch processing (up to 1M rows)
• Vertica-Optimized: Projection awareness, columnar query support
• Production Ready: Connection pooling, SSL support, timeout configuration
• Parameter Binding: SQL injection protection
• Persistent Connection: Reuses a single connection with configurable idle timeout
• Load Balancing: Optional redirect to optimal Vertica node on connect

Available Tools

Query Execution

• execute_query: Execute SQL with optional parameters
• stream_query: Handle large datasets with configurable batching

Schema Discovery

• get_table_structure: Table columns, types, constraints
• list_tables: All tables in schema with metadata
• list_views: All views with definitions
• list_indexes: Vertica projections for optimization

Support

• Issues: GitHub Issues
• Releases: GitHub Releases

Quick Start

Claude Code

claude mcp add vertica --scope user -- npx -y @hechtcarmel/vertica-mcp@latest  --env-file /path/to/your/.env

Create your .env file with connection details:

VERTICA_HOST=your-vertica-host.com
VERTICA_PORT=5433
VERTICA_DATABASE=your_database
VERTICA_USER=your_username
VERTICA_PASSWORD=your_password

Cursor

1. Create environment file ~/.cursor/vertica.env:

VERTICA_HOST=your-vertica-host.com
VERTICA_PORT=5433
VERTICA_DATABASE=your_database
VERTICA_USER=your_username
VERTICA_PASSWORD=your_password

2. Configure ~/.cursor/mcp.json:

{
  "mcpServers": {
    "vertica-mcp": {
      "command": "npx",
      "args": [
        "@hechtcarmel/vertica-mcp",
        "--env-file",
        "/Users/yourusername/.cursor/vertica.env"
      ]
    }
  }
}

3. Restart Cursor

Claude Desktop

macOS: ~/Library/Application Support/Claude/claude_desktop_config.json Windows: %APPDATA%/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "vertica-mcp": {
      "command": "npx",
      "args": [
        "@hechtcarmel/vertica-mcp",
        "--env-file",
        "/path/to/your/.env"
      ]
    }
  }
}

Configuration

Required Variables

VERTICA_HOST          # Database hostname
VERTICA_DATABASE      # Database name
VERTICA_USER          # Username

Optional Variables

VERTICA_PORT=5433                      # Default: 5433
VERTICA_PASSWORD                       # Password (optional)
VERTICA_READONLY_MODE=true             # Default: true
VERTICA_QUERY_TIMEOUT=60000            # Default: 60000ms
VERTICA_IDLE_TIMEOUT=3600000           # Default: 3600000ms (1h), range: 60s-24h
VERTICA_SSL=false                      # Default: false
VERTICA_SSL_REJECT_UNAUTHORIZED=true   # Default: true
VERTICA_DEFAULT_SCHEMA=public          # Default: public
VERTICA_CONNECTION_LOAD_BALANCE=false  # Default: false

Enabling Write Operations

To allow INSERT/UPDATE/DELETE/CREATE/DROP operations:

VERTICA_READONLY_MODE=false

Warning: Only disable readonly mode if you understand the implications.

Persistent Connection & Idle Timeout

The server reuses a single connection across tool calls. If idle for longer than VERTICA_IDLE_TIMEOUT, it disconnects automatically and reconnects on next use.

VERTICA_IDLE_TIMEOUT=3600000  # 1 hour (default), min: 60000ms, max: 86400000ms

Connection Load Balancing

When enabled, the server queries Vertica's DESCRIBE_LOAD_BALANCE_DECISION on first connect and transparently reconnects to the optimal node if a redirect is available, matching the behavior of Vertica JDBC/ODBC drivers.

VERTICA_CONNECTION_LOAD_BALANCE=true

Note: Requires that the redirect IP is reachable from the MCP server host.

Usage Examples

Query Data

SELECT customer_state, COUNT(*) as count
FROM customer_dimension
GROUP BY customer_state
ORDER BY count DESC
LIMIT 10;

Explore Schema

SHOW TABLES;
DESCRIBE customer_dimension;

Analyze Performance

EXPLAIN SELECT * FROM store_sales_fact
WHERE sale_date_key > '2023-01-01';

Stream Large Results

When querying large datasets, use the stream_query tool:

• Default batch size: 1000 rows
• Configurable batch size: 1-10,000 rows
• Maximum rows: 1,000,000

Requirements

• Node.js >= 18.0.0
• Vertica database (any recent version)
• Network access to Vertica server

Troubleshooting

Connection Failed

# Test connectivity directly
vsql -h localhost -p 5433 -d VMart -U dbadmin

Verify:

• Host and port are reachable
• Database credentials are correct
• User has required permissions

Permission Errors

• User needs SELECT permissions on tables
• User needs access to system catalogs (v_catalog.*)

Query Timeouts

Increase timeout for complex queries:

VERTICA_QUERY_TIMEOUT=300000  # 5 minutes

Large Result Sets

Use stream_query instead of execute_query for queries returning >10,000 rows.

Load Balance Redirect Fails

If VERTICA_CONNECTION_LOAD_BALANCE=true but routing fails, the server logs a warning and stays on the initial host - no error is returned to the client. Check that all Vertica cluster nodes are reachable from the MCP server.

License

MIT License - see LICENSE file.