Vertica

MCP Vertica
  • hcl

0

GitHub Stars

hcl

Language

7 months ago

First Indexed

3 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs

You run the Vertica MCP server on AWS to build a two-stack, isolated CI/CD environment. The MCP stack hosts a FastAPI server that communicates with Vertica running in a separate DB stack. This enables you to render queries and perform health checks through a dedicated HTTP or local stdio transport, while keeping the data plane and control plane separate for reliability and cost control.

How to use

Connect to the MCP server using either the local stdio transport or the remote HTTP transport. The local flow is convenient for development and testing on your workstation, while the remote HTTP flow lets you access the MCP server from anywhere with proper security.

{
  "mcpServers": {
    "vertica-local": {
      "command": "uvx",
      "args": ["mcp-vertica", "--transport", "stdio"]
    }
  }
}

Using the local stdio transport (Claude Desktop style)

In local development you can run the MCP server via a stdio transport. This keeps the MCP process on your machine and uses the uvx tool to launch the server with stdio logging.

{
  "mcpServers": {
    "vertica-local": {
      "command": "uvx",
      "args": ["mcp-vertica", "--transport", "stdio"]
    }
  }
}

Using the remote HTTP transport (beta)

If you want to reach the MCP server over HTTP, use the remote transport. This allows clients to connect via the MCP HTTP endpoint at the server URL.

{
  "mcpServers": {
    "vertica-remote": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "http://<MCP-PUBLIC-IP>:8000/sse"],
      "env": {
        "AUTH_HEADER": "Authorization: Bearer <MCP_HTTP_TOKEN>"
      }
    }
  }
}

Endpoints you can call

The MCP server exposes health and query endpoints to verify readiness and run rendering or SQL rendering requests.

Health and readiness checks

Use the health endpoint to confirm the MCP server is responsive and connected to Vertica. Run a simple health check to ensure the API is up and ready to render queries.

Available tools

healthz

GET /healthz endpoint to verify MCP server readiness and health.

render

POST /api/render endpoint to render content via MCP rendering capabilities.

query

POST /api/query endpoint to execute a SQL query against Vertica and return results.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational