Cube.dev MCP Server for WindsurfGive Windsurf 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

Windsurf brings agentic AI coding to a purpose-built IDE. Connect Cube.dev through Vinkius and Cascade will auto-discover every tool. ask questions, generate code, and act on live data without leaving your editor.

Ask AI about this MCP Server for Windsurf

Open in ChatGPT Open in Claude Open in Perplexity

The Cube.dev MCP Server for Windsurf 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.

Windsurf's Cascade agent chains multiple Cube.dev tool calls autonomously. query data, analyze results, and generate code in a single agentic session. Paste Vinkius Edge URL, reload, and all 15 tools are immediately available. Real-time tool feedback appears inline, so you see API responses directly in your editor.

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 Windsurf via MCP

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

Open MCP Settings

Go to Settings → MCP Configuration or press Cmd+Shift+P and search "MCP"

Add the server

Paste the JSON configuration above into mcp_config.json

Save and reload

Windsurf will detect the new server automatically

Start using Cube.dev

Open Cascade and ask: "Using Cube.dev, help me...". 15 tools available

Why Use Windsurf with the Cube.dev MCP Server

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

Windsurf's Cascade agent autonomously chains multiple tool calls in sequence, solving complex multi-step tasks without manual intervention

Purpose-built for agentic workflows. Cascade understands context across your entire codebase and integrates MCP tools natively

JSON-based configuration means zero code changes: paste a URL, reload, and all 15 tools are immediately available

Real-time tool feedback is displayed inline, so you see API responses directly in your editor without switching contexts

Cube.dev + Windsurf Use Cases

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

Automated code generation: ask Cascade to fetch data from Cube.dev and generate models, types, or handlers based on real API responses

Live debugging: query Cube.dev tools mid-session to inspect production data while debugging without leaving the editor

Documentation generation: pull schema information from Cube.dev and have Cascade generate comprehensive API docs automatically

Rapid prototyping: combine Cube.dev data with Cascade's code generation to scaffold entire features in minutes

Example Prompts for Cube.dev in Windsurf

Ready-to-use prompts you can give your Windsurf 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 Windsurf

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

Server not connecting

Check Settings → MCP for the server status. Try toggling it off and on.

Cube.dev + Windsurf FAQ

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

How does Windsurf discover MCP tools?

Windsurf reads the mcp_config.json file on startup and connects to each configured server via Streamable HTTP. Tools are listed in the MCP panel and available to Cascade automatically.

Can Cascade chain multiple MCP tool calls?

Yes. Cascade is an agentic system. it can plan and execute multi-step workflows, calling several tools in sequence to accomplish complex tasks without manual prompting between steps.

Does Windsurf support multiple MCP servers?

Yes. Add as many servers as needed in mcp_config.json. Each server's tools appear in the MCP panel and Cascade can use tools from different servers in a single flow.