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 Claude Code?
Claude Code registers Cube.dev as an MCP server in a single terminal command. Once connected, Claude Code discovers all 15 tools at runtime and can call them headlessly. ideal for CI/CD pipelines, cron jobs, and automated workflows where Cube.dev data drives decisions without human intervention.
- —
Single-command setup:
claude mcp addregisters the server instantly. no config files to edit or applications to restart - —
Terminal-native workflow means MCP tools integrate seamlessly into shell scripts, CI/CD pipelines, and automated DevOps tasks
- —
Claude Code runs headlessly, enabling unattended batch processing using Cube.dev tools in cron jobs or deployment scripts
- —
Built by the same team that created the MCP protocol, ensuring first-class compatibility and the fastest adoption of new protocol features
Cube.dev in Claude Code
Cube.dev and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect Cube.dev to Claude Code 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 Claude Code
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 Claude Code 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 Claude Code
Every tool call from Claude Code 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 do I add an MCP server to Claude Code?
Run claude mcp add <name> --transport http "<url>" in your terminal. Claude Code registers the server and discovers all tools immediately.
Can Claude Code run MCP tools in headless mode?
Yes. Claude Code supports non-interactive execution, making it ideal for scripts, cron jobs, and CI/CD pipelines that need MCP tool access.
How do I list all connected MCP servers?
Run claude mcp in your terminal to see all registered servers and their status, or type /mcp inside an active Claude Code session.
Command not found: claude
Ensure Claude Code is installed globally: npm install -g @anthropic-ai/claude-code
Connection timeout
Check your internet connection and verify the Edge URL is reachable
Explore More MCP Servers
View all →
Poplar
11 toolsAutomate programmatic direct mail via Poplar — trigger mailers, standardize addresses, and manage audiences directly from any AI agent.

Cohere
6 toolsAccess Cohere AI models via API — chat with Command models, generate embeddings, rerank documents and tokenize text from any AI agent.

Vertex AI Vector Search
6 toolsBring Google's massive vector matching power to your AI agent. Search billions of semantic embeddings and administer Vertex Index endpoints directly in chat.

Freshdesk
10 toolsResolve customer tickets faster with omnichannel helpdesk tools, smart automation, and self-service portals your users will love.
