Mcp Vertica

What is Mcp Vertica about?

Mcp Vertica offers an MCP server that connects to Vertica databases, handling connection pooling, SSL/TLS, and permission controls while exposing tools for query execution, data streaming, bulk copy, and schema inspection.

How to use Mcp Vertica?

1. Install the server via npm:

   npx -y @nolleh/mcp-vertica
   

2. Configure the server in your MCP client configuration file (e.g., uvx config) with the required environment variables such as VERTICA_HOST, VERTICA_PORT, VERTICA_DATABASE, VERTICA_USER, and VERTICA_PASSWORD.
3. Run the server using the configured command (e.g., uvx mcp-vertica or Docker) and connect your client.

Key features of Mcp Vertica

• Connection pooling with configurable limits
• SSL/TLS support and optional certificate validation
• Automatic cleanup and timeout handling
• Execute arbitrary SQL queries
• Stream large result sets in configurable batch sizes
• Bulk data loading with Vertica COPY command
• Transaction management (BEGIN, COMMIT, ROLLBACK)
• Detailed schema introspection: tables, indexes, views, constraints, columns
• Fine‑grained operation permissions (INSERT, UPDATE, DELETE, DDL)
• Schema‑specific permission settings
• Password masking in logs for security

Use cases of Mcp Vertica

• Integrating Vertica data sources into AI assistants or agents that rely on MCP
• Building data pipelines that need high‑throughput bulk loading into Vertica
• Developing analytics dashboards that require streaming query results
• Automating database schema audits and documentation
• Enforcing security policies for multi‑tenant environments

FAQ from the Mcp Vertica

Q: Which command should I use to start the server? A: The preferred method is npx -y @nolleh/mcp-vertica. Alternatively, you can run the pre‑built Docker image nolleh/mcp-vertica.

Q: How do I enable SSL? A: Set VERTICA_SSL=true and optionally VERTICA_SSL_REJECT_UNAUTHORIZED=true in the environment variables.

Q: Can I limit the number of concurrent connections? A: Yes, adjust VERTICA_CONNECTION_LIMIT to the desired maximum.

Q: How are operation permissions controlled? A: Use environment variables like ALLOW_INSERT_OPERATION, ALLOW_UPDATE_OPERATION, ALLOW_DELETE_OPERATION, and ALLOW_DDL_OPERATION (true/false). Schema‑specific permissions can be set with variables such as SCHEMA_INSERT_PERMISSIONS.

Q: What should I do if the server fails to connect? A: Run uv cache clean to clear cached binaries and retry the connection.

MCP Vertica

A Vertica MCP(model-context-protocol) Server

[!IMPORTANT] If you have troubles to connect this mcp server, try to run uv cache clean, and then retry.

Example: MCP Server Setting

Create or edit the file your mcp client config file with the following content:

UVX

{
  "mcpServers": {
    "vertica": {
      "command": "uvx",
      "args": ["mcp-vertica"],
      "env": {
        "VERTICA_HOST": "localhost",
        "VERTICA_PORT": 5433,
        "VERTICA_DATABASE": "VMart",
        "VERTICA_USER": "dbadmin",
        "VERTICA_PASSWORD": "test_password",
        "VERTICA_CONNECTION_LIMIT": 10,
        "VERTICA_SSL": false,
        "VERTICA_SSL_REJECT_UNAUTHORIZED": true
      }
    }
  }
}

Or with args

{
  "mcpServers": {
    "vertica": {
      "command": "uvx",
      "args": [
        "mcp-vertica",
        "--host=localhost",
        "--db-port=5433",
        "--database=VMart",
        "--user=dbadmin",
        "--password=test_password",
        "--connection-limit=10"
      ]
    }
  }
}

Docker

{
  "mcpServers": {
    "vertica": {
      "command": "docker",
      "args": ["run", "-i", "--rm", "nolleh/mcp-vertica"],
      "env": {
        "VERTICA_HOST": "localhost",
        "VERTICA_PORT": 5433,
        "VERTICA_DATABASE": "VMart",
        "VERTICA_USER": "dbadmin",
        "VERTICA_PASSWORD": "test_password",
        "VERTICA_CONNECTION_LIMIT": 10,
        "VERTICA_SSL": false,
        "VERTICA_SSL_REJECT_UNAUTHORIZED": true
      }
    }
  }
}

[!Note]

• For boolean flags like --ssl or --ssl-reject-unauthorized, simply add the flag (e.g., "--ssl") to enable it, or omit it to disable.
• For an empty password, use an empty string as shown above.

Features

Database Connection Management

• Connection pooling with configurable limits
• SSL/TLS support
• Automatic connection cleanup
• Connection timeout handling

Query Operations

• Execute SQL queries
• Stream large query results in batches
• Copy data operations
• Transaction management

Schema Management

• Table structure inspection
• Index management
• View management
• Constraint information
• Column details

Security Features

• Operation-level permissions (INSERT, UPDATE, DELETE, DDL)
• Schema-specific permissions
• SSL/TLS support
• Password masking in logs

Tools

Database Operations

1. execute_query

   • Execute SQL queries
   • Support for all SQL operations

2. stream_query

   • Stream large query results in batches
   • Configurable batch size

3. copy_data

   • Bulk data loading using COPY command
   • Efficient for large datasets

Schema Management

1. get_table_structure

   • Get detailed table structure
   • Column information
   • Constraints

2. list_indexes

   • List all indexes for a table
   • Index type and uniqueness
   • Column information

3. list_views

   • List all views in a schema
   • View definitions

Configuration

Environment Variables

VERTICA_HOST=localhost
VERTICA_PORT=5433
VERTICA_DATABASE=VMart
VERTICA_USER=newdbadmin
VERTICA_PASSWORD=vertica
VERTICA_CONNECTION_LIMIT=10
VERTICA_SSL=false
VERTICA_SSL_REJECT_UNAUTHORIZED=true

Operation Permissions

ALLOW_INSERT_OPERATION=false
ALLOW_UPDATE_OPERATION=false
ALLOW_DELETE_OPERATION=false
ALLOW_DDL_OPERATION=false

Schema Permissions

SCHEMA_INSERT_PERMISSIONS=schema1:true,schema2:false
SCHEMA_UPDATE_PERMISSIONS=schema1:true,schema2:false
SCHEMA_DELETE_PERMISSIONS=schema1:true,schema2:false
SCHEMA_DDL_PERMISSIONS=schema1:true,schema2:false

Installation

Installing via Smithery

To install Vertica Database Connector for Claude Desktop automatically via Smithery:

npx -y @smithery/cli install @nolleh/mcp-vertica --client claude

Installing Manually

Open your favorite mcp client's config file, then configure with uvx mcp-vertica

Example: Mcp Server Setting

Development

Appendix: For Testing, VerticaDB Docker Compose Example

version: "3.8"

services:
  vertica:
    # image: vertica/vertica-ce:11.1.0-0
    image: vertica/vertica-ce:latest
    platform: linux/amd64
    container_name: vertica-ce
    environment:
      VERTICA_MEMDEBUG: 2
    ports:
      - "5433:5433"
      - "5444:5444"
    volumes:
      - vertica_data:/home/dbadmin/VMart
    healthcheck:
      test:
        [
          "CMD",
          "/opt/vertica/bin/vsql",
          "-h",
          "localhost",
          "-d",
          "VMart",
          "-U",
          "dbadmin",
          "-c",
          "SELECT 1",
        ]
      interval: 10s
      timeout: 5s
      retries: 5
      start_period: 30s
    restart: unless-stopped

volumes:
  vertica_data:
    driver: local

Then run server by following instruction Example: Mcp Server Setting, Then see everything works as fine

License

This project is licensed under the MIT License - see the LICENSE file for details.