You can run the MCP server outside of Kubernetes and connect it to a Vertica database that is running inside Kubernetes. This setup allows you to execute SQL queries through the MCP server today. However, if your goal is to deploy the MCP server inside Kubernetes and use it to perform database operations (such as adding a subcluster), full in‑cluster MCP functionality will be available starting with the Vertica 26.3 release.
Environment
- Product: Vertica Analytics Platform
- Feature: Management Command Protocol (MCP)
- Deployment Model: VerticaDB running on Kubernetes
- MCP server: External (today) or in‑cluster (26.3+)
Situation
A customer wants to use the MCP server with VerticaDB running in Kubernetes.
Two scenarios were evaluated:
-
Running MCP outside Kubernetes → Works today
- MCP server can connect to a VerticaDB running on Kubernetes.
- SQL queries and standard MCP functions work.
-
Running MCP inside Kubernetes → Requires Vertica 26.3
- Database operations like adding a subcluster via MCP inside Kubernetes are not supported pre‑26.3.
