Vertica MCP Server
Provides read-only access to Vertica databases.
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
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
- 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
- Configure
~/.cursor/mcp.json:
{
"mcpServers": {
"vertica-mcp": {
"command": "npx",
"args": [
"@hechtcarmel/vertica-mcp",
"--env-file",
"/Users/yourusername/.cursor/vertica.env"
]
}
}
}
- 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_CONNECTION_LIMIT=10 # Default: 10 (max: 100)
VERTICA_QUERY_TIMEOUT=60000 # Default: 60000ms
VERTICA_SSL=false # Default: false
VERTICA_SSL_REJECT_UNAUTHORIZED=true # Default: true
VERTICA_DEFAULT_SCHEMA=public # Default: public
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.
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
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
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.
Requirements
- Node.js >= 18.0.0
- Vertica database (any recent version)
- Network access to Vertica server
Support
- Issues: GitHub Issues
- Releases: GitHub Releases
License
MIT License - see LICENSE file.
Acknowledgments
This project's architecture and tool design are based on mcp-vertica by @nolleh.
Current Version: 1.3.5
相关服务器
Engram
Persistent memory layer for AI agents with semantic search, consolidation, and cross-session intelligence via MCP.
DynamoDB-Toolbox
Leverages your Schemas and Access Patterns to interact with your DynamoDB Database using natural language.
mnemon-mcp
Persistent layered memory for AI agents — 4-layer model, FTS5 search, fact versioning, EN+RU stemming. Local-first, zero-cloud, single SQLite file.
KnowledgeGraph MCP Server
Enables persistent knowledge storage for Claude using a knowledge graph with multiple database backends like PostgreSQL and SQLite.
Octopus MCP Server
A high-performance, persistent knowledge base MCP server built with Rust. Supports local deployment with hybrid datastores like Qdrant, Neo4j, and Redis.
IMF Data MCP
Retrieve and process economic data from the International Monetary Fund (IMF) API, including datasets, time series, indicators, and countries.
GraphDB
Provides read-only access to an Ontotext GraphDB repository.
BigCommerce by CData
A read-only MCP server for BigCommerce, enabling LLMs to query live data using the CData JDBC Driver.
Michelin MCP
Access structured Michelin restaurant data, including cities, countries, cuisines, awards, and facilities.
Datai MCP Server
Provides real-time wallet portfolio data, including DeFi, token, and NFT holdings, using the Datai API.