How to Use the Cube.dev MCP in VS Code Copilot

Q: How do I share the Cube.dev MCP server with my team in VS Code Copilot?

Add the Vinkius endpoint to .vscode/mcp.json and commit it to your repository. Everyone gets the tools automatically.

Q: Can VS Code Copilot check my Cube.dev deployment status?

Yes. listenvironments and checkready allow the agent to verify infrastructure health before writing dependent code.

Q: Why does VS Code Copilot fail to load Cube.dev data?

The agent needs a valid CUBECLOUDAPIKEY to access cloud deployments. Ensure your local environment variables match the required configuration.

Q: Does this support generating metadata tokens?

generatemetatoken creates a JWT for the Metadata API. You can use this to build custom internal tooling around your schema.

Give your entire engineering team shared access to your Cube.dev semantic layer inside VS Code Copilot via MCP.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Cube.dev MCP to VS Code Copilot

Create your Vinkius account to connect Cube.dev to VS Code Copilot and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup Cube.dev with VS Code Copilot

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Query Semantic Data via VS Code Copilot

`load_query` executes requests against your semantic layer and returns the aggregated results. When a developer asks Copilot how to format a chart, the agent fetches the actual data shape to write the correct mapping logic. `get_entity` retrieves the exact metadata for specific cubes. Your team stops guessing which measures are available because the agent reads the schema directly from the source.

Team-Wide Schema Discovery

`list_data_sources` shows every configured database connected to your deployment. New hires can ask the agent where the sales data lives, and it will list the exact connections without requiring a wiki search. `get_meta` pulls the complete catalog of cubes and views. You commit the MCP server config to your repository, and suddenly everyone has instant access to the entire business logic definitions.

Debug and Manage Infrastructure

`get_sql` exposes the raw database queries generated by your semantic layer. If a specific dashboard widget is timing out, developers can inspect the underlying SQL right in their editor using this MCP Server. `check_live` pings the deployment to ensure it is responsive. Before someone spends an hour debugging a network request, Copilot verifies the target environment is actually up.

Setup guide

Set up Cube.dev MCP in VS Code Copilot

Prerequisites

VS Code 1.99 or later with GitHub Copilot extension
Active Vinkius subscription with a valid endpoint token

1

Open MCP configuration

Open the Command Palette (Cmd+Shift+P / Ctrl+Shift+P) and run "MCP: Add Server". Select HTTP (Streamable) as the server type. VS Code will create .vscode/mcp.json in your workspace.
2

Add the Cube.dev MCP

Paste the JSON snippet shown on the right into your .vscode/mcp.json. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com.
3

Switch to Agent mode

Open Copilot Chat (Cmd+Shift+I / Ctrl+Shift+I) and switch to Agent mode using the dropdown. MCP tools are only available in Agent mode — they do not appear in Edit or Ask modes.
4

Verify the connection

In the Copilot Chat input, type # to list available tools. You should see the Cube.dev tools listed. Try asking: "List my recent Cube.dev transactions" and Copilot will invoke them automatically.

.vscode/mcp.json

{
  "mcpServers": {
    "cubedev-mcp": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Cube.dev. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect Cube.dev now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about Cube.dev MCP in VS Code Copilot

Add the Vinkius endpoint to `.vscode/mcp.json` and commit it to your repository. Everyone gets the tools automatically.

Yes. `list_environments` and `check_ready` allow the agent to verify infrastructure health before writing dependent code.

The agent needs a valid `CUBE_CLOUD_API_KEY` to access cloud deployments. Ensure your local environment variables match the required configuration.

`generate_meta_token` creates a JWT for the Metadata API. You can use this to build custom internal tooling around your schema.

The server handles pre-aggregation statuses, generated SQL strings, and dimension metadata. Vinkius routes this traffic through ephemeral, isolated containers that never log your proprietary business logic.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript