Cube.dev MCP Server for CursorGive Cursor 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

Cursor is an AI-first code editor built on VS Code that integrates LLM-powered coding assistance directly into the development workflow. Its Agent mode enables autonomous multi-step coding tasks, and MCP support lets agents access external data sources and APIs during code generation.

Ask AI about this MCP Server for Cursor

Open in ChatGPT Open in Claude Open in Perplexity

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

Cursor's Agent mode turns Cube.dev into an in-editor superpower. Ask Cursor to generate code using live data from Cube.dev and it fetches, processes, and writes. all in a single agentic loop. 15 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.

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

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

Open MCP Settings

Press Cmd+Shift+P (macOS) or Ctrl+Shift+P (Windows/Linux) → search "MCP Settings"

Add the server config

Paste the JSON configuration above into the mcp.json file that opens

Save the file

Cursor will automatically detect the new MCP server

Start using Cube.dev

Open Agent mode in chat and ask: "Using Cube.dev, help me...". 15 tools available

Why Use Cursor with the Cube.dev MCP Server

Cursor AI Code Editor provides unique advantages when paired with Cube.dev through the Model Context Protocol.

Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context

Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards

MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment

VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools

Cube.dev + Cursor Use Cases

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

Code generation with live data: ask Cursor to generate a security report module using live DNS and subdomain data fetched through MCP

Automated documentation: have Cursor query your API's tool schemas and generate TypeScript interfaces or OpenAPI specs automatically

Infrastructure-as-code: Cursor can fetch domain configurations and generate corresponding Terraform or CloudFormation templates

Test scaffolding: ask Cursor to pull real API responses via MCP and generate unit test fixtures from actual data

Example Prompts for Cube.dev in Cursor

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

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

Tools not appearing in Cursor

Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.

Server shows as disconnected

Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.

Cube.dev + Cursor FAQ

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

What is Agent mode and why does it matter for MCP?

Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.

Where does Cursor store MCP configuration?

Cursor looks for MCP server configurations in a mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.

Can Cursor use MCP tools in inline edits?

No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design. tool calls require user visibility and approval.

How do I verify MCP tools are loaded?

Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.

Explore More MCP Servers

View all →

Grafana k6 Cloud (Load Testing)

10 tools

Manage load tests via k6 Cloud — run tests, monitor performance metrics, and audit thresholds.

Venue

10 tools

Manage event venues with booking calendars, client contracts, and catering coordination for wedding and conference spaces.

Routific

10 tools

Connect your AI assistant to Routific to solve complex vehicle routing problems, dispatch drivers, and manage global delivery timelines natively through chat.

Telebroad

12 tools

Connect your business phone system with cloud PBX that includes auto-attendant, call queues, and voicemail-to-email transcription.