Cube.dev MCP Server for ClineGive Cline instant access to 15 tools to Check Live, Check Ready, Convert Query, and more

Name: Cube.dev
Price: 29 USD
Availability: InStock
Rating: 0.2 (1 reviews)
Author: Vinkius

GDPR Free for Subscribers

Cline is an autonomous AI coding agent inside VS Code that plans, executes, and iterates on tasks. Wire Cube.dev through Vinkius and Cline gains direct access to every tool. from data retrieval to workflow automation. without leaving the terminal.

Ask AI about this MCP Server for Cline

Open in ChatGPT Open in Claude Open in Perplexity

The Cube.dev MCP Server for Cline is a standout in the Brain Trust category — giving your AI agent 15 tools to work with, ready to go from day one.

Built for AI Agents by Vinkius

Vinkius delivers Streamable HTTP and SSE to any MCP client

Claude

ChatGPT

Cursor

Gemini

Windsurf

VS Code

JetBrains

Vercel

+ other MCP clients

Classic Setup·json

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

RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install Cube.dev and 4,000+ MCP Servers from a single visual interface.

Download Free Open SourceNo signup required

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* 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

About 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.

Cline operates autonomously inside VS Code. it reads your codebase, plans a strategy, and executes multi-step tasks including Cube.dev tool calls without waiting for prompts between steps. Connect 15 tools through Vinkius and Cline can fetch data, generate code, and commit changes in a single autonomous run.

What you can do

Data Querying — Execute complex REST API queries using load_query to fetch aggregated data with measures, dimensions, and filters.
SQL Inspection — Use get_sql and execute_cube_sql to debug or run raw queries against the SQL API for deep data investigation.
Metadata Exploration — Retrieve cube definitions, views, and segments via get_meta to understand your data model without leaving the chat.
Performance Management — Trigger and monitor background pre-aggregation builds with trigger_pre_aggregation_job to ensure your dashboards stay fast.
Cloud Management — List deployments and environments if using Cube Cloud to manage your infrastructure context.

trigger

Trigger pre aggregation job on Cube.dev

Trigger a pre-aggregation build job

Connect Cube.dev to Cline via MCP

Follow these steps to wire Cube.dev into Cline. The entire setup takes under two minutes — your credentials stay safe behind Vinkius.

Open Cline MCP Settings

Click the MCP Servers icon in the Cline sidebar panel

Add remote server

Click "Add MCP Server" and paste the configuration above

Enable the server

Toggle the server switch to ON

Start using Cube.dev

Ask Cline: "Using Cube.dev, help me...". 15 tools available

Why Use Cline with the Cube.dev MCP Server

Cline provides unique advantages when paired with Cube.dev through the Model Context Protocol.

Cline operates autonomously. it reads your codebase, plans a strategy, and executes multi-step tasks including MCP tool calls without step-by-step prompts

Runs inside VS Code, so you get MCP tool access alongside your existing extensions, terminal, and version control in a single window

Cline can create, edit, and delete files based on MCP tool responses, enabling end-to-end automation from data retrieval to code generation

Transparent execution: every tool call and file change is shown in Cline's activity log for full visibility and approval before committing

Cube.dev + Cline Use Cases

Practical scenarios where Cline combined with the Cube.dev MCP Server delivers measurable value.

Autonomous feature building: tell Cline to fetch data from Cube.dev and scaffold a complete module with types, handlers, and tests

Codebase refactoring: use Cube.dev tools to validate live data while Cline restructures your code to match updated schemas

Automated testing: Cline fetches real responses from Cube.dev and generates snapshot tests or mocks based on actual payloads

Incident response: query Cube.dev for real-time status and let Cline generate hotfix patches based on the findings

Example Prompts for Cube.dev in Cline

Ready-to-use prompts you can give your Cline agent to start working with Cube.dev immediately.

"Show me the metadata for all available cubes and views."

"Run a query to get the total count of orders grouped by status for the last 30 days."

"Trigger a pre-aggregation build for the 'Sales' cube."

Troubleshooting Cube.dev MCP Server with Cline

Common issues when connecting Cube.dev to Cline through Vinkius, and how to resolve them.

Server shows error in sidebar

Click the server name to see logs. Verify the URL and token are correct.

Cube.dev + Cline FAQ

Common questions about integrating Cube.dev MCP Server with Cline.

How does Cline connect to MCP servers?

Cline reads MCP server configurations from its settings panel in VS Code. Add the server URL and Cline discovers all available tools on initialization.