Compatible with every major AI agent and IDE
What is the Cube.dev MCP Server?
Connect your Cube.dev instance to any AI agent to bridge the gap between natural language and your data warehouse. This server allows your agent to interact with Cube's semantic layer, ensuring consistent metrics and high-performance data retrieval.
What you can do
- Data Querying — Execute complex REST API queries using
load_queryto fetch aggregated data with measures, dimensions, and filters. - SQL Inspection — Use
get_sqlandexecute_cube_sqlto debug or run raw queries against the SQL API for deep data investigation. - Metadata Exploration — Retrieve cube definitions, views, and segments via
get_metato understand your data model without leaving the chat. - Performance Management — Trigger and monitor background pre-aggregation builds with
trigger_pre_aggregation_jobto ensure your dashboards stay fast. - Cloud Management — List deployments and environments if using Cube Cloud to manage your infrastructure context.
How it works
- Subscribe to this server
- Provide your Cube API URL and Secret Token
- Start asking questions about your data metrics and model structure
Who is this for?
- Data Engineers — quickly verify data models and trigger cache refreshes via CLI or AI interface.
- Analytics Engineers — debug generated SQL and inspect metadata to ensure metric consistency.
- Product Managers — get instant answers to data questions by letting the AI query the semantic layer directly.
Built-in capabilities (15)
Check if Cube deployment is live
Check if Cube deployment is ready
Convert a SQL query to a REST API query format
Execute a raw SQL query against the SQL API
Requires CUBE_CLOUD_API_KEY. Generate a JWT for the Metadata API
Get detailed metadata for a specific entity
Get metadata for cubes and views
Get status of pre-aggregation jobs
Useful for debugging. Get generated SQL for a Cube query
List configured data sources
Requires CUBE_CLOUD_API_KEY. List all Cube Cloud deployments
List all cubes and views
Requires CUBE_CLOUD_API_KEY. List environments for a deployment
Use this to get aggregated data. Execute a Cube query and return results
Trigger a pre-aggregation build job
Why Pydantic AI?
Pydantic AI validates every Cube.dev tool response against typed schemas, catching data inconsistencies at build time. Connect 15 tools through Vinkius and switch between OpenAI, Anthropic, or Gemini without changing your integration code. full type safety, structured output guarantees, and dependency injection for testable agents.
- —
Full type safety: every MCP tool response is validated against Pydantic models, catching data inconsistencies before they reach your application
- —
Model-agnostic architecture. switch between OpenAI, Anthropic, or Gemini without changing your Cube.dev integration code
- —
Structured output guarantee: Pydantic AI ensures tool results conform to defined schemas, eliminating runtime type errors
- —
Dependency injection system cleanly separates your Cube.dev connection logic from agent behavior for testable, maintainable code
Cube.dev in Pydantic AI
Cube.dev and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect Cube.dev to Pydantic AI through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 4,000+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for Cube.dev in Pydantic AI
The Cube.dev MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 15 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in Pydantic AI only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
How Vinkius secures
Cube.dev for Pydantic AI
Every tool call from Pydantic AI to the Cube.dev MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I see the exact SQL that Cube generates for a specific query?
Yes. You can use the get_sql tool. By providing the query JSON, the agent will return the generated SQL string, which is perfect for debugging or verifying your data logic.
How do I refresh the data cache or pre-aggregations using the AI?
You can use the trigger_pre_aggregation_job tool. You can specify which cubes or data sources to target, and the agent will initiate the background build process for you.
Is it possible to explore the available measures and dimensions?
Absolutely. Use the get_meta tool to fetch all metadata. This allows the AI to understand what data is available to be queried, including views and segments.
How does Pydantic AI discover MCP tools?
Create an MCPServerHTTP instance with the server URL. Pydantic AI connects, discovers all tools, and generates typed Python interfaces automatically.
Does Pydantic AI validate MCP tool responses?
Yes. When you define result types as Pydantic models, every tool response is validated against the schema. Invalid data raises a clear error instead of silently corrupting your pipeline.
Can I switch LLM providers without changing MCP code?
Absolutely. Pydantic AI abstracts the model layer. your Cube.dev MCP integration works identically with OpenAI, Anthropic, Google, or any supported provider.
MCPServerHTTP not found
Update: pip install --upgrade pydantic-ai
Explore More MCP Servers
View all →
ProjectManager
11 toolsAutomate project planning and tracking via ProjectManager — manage projects, tasks, and timesheets directly from any AI agent.

Vinsight
12 toolsManage wine, beer, and spirits production — inventory, sales orders, batches, vessels, and lab results for your Vinsight operation through natural conversation.

CustomerGauge
10 toolsEquip your AI agent to manage B2B experience, monitor NPS scores, and track revenue impact directly via the CustomerGauge API.

Hexomatic
11 toolsAutomate web scraping and worklfows via Hexomatic — manage workflows, recipes, and automation logs directly from any AI agent.
