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 VS Code Copilot?
GitHub Copilot Agent mode brings Cube.dev data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 15 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.
- —
VS Code is used by over 70% of developers. adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor
- —
Project-scoped MCP configs (
.vscode/mcp.json) let you commit server configurations to your repository, ensuring the entire team shares the same tool access - —
Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop
- —
GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services
Cube.dev in VS Code Copilot
Cube.dev and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect Cube.dev to VS Code Copilot 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 VS Code Copilot
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 VS Code Copilot 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 VS Code Copilot
Every tool call from VS Code Copilot 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.
Which VS Code version supports MCP?
MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.
How do I switch to Agent mode?
Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.
Can I restrict which MCP tools Copilot can access?
Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.
Does MCP work in VS Code Remote or Codespaces?
Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.
MCP tools not available
Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.
Explore More MCP Servers
View all →
WordPress Subscriber Creator
1 toolsThis MCP does exactly one thing: it registers a new user in your WordPress database with the strictly enforced 'Subscriber' role. Perfect for turning Claude into an automated lead generation or membership onboarding bot.
Helicone (LLM Observability)
10 toolsMonitor LLM usage via Helicone — track requests, analyze costs, measure latency, and manage prompts.

Argo CD (GitOps)
13 toolsManage Kubernetes deployments via Argo CD — sync applications, check logs, and manage clusters/repositories directly from your AI agent.

ContentStudio
13 toolsPlan, create, and schedule social media content across all channels with AI writing assistance and performance analytics.
