4,000+ servers built on vurb.ts
Vinkius

Cube.dev MCP Server for Claude DesktopGive Claude Desktop instant access to 15 tools to Check Live, Check Ready, Convert Query, and more

MCP Inspector GDPR Free for Subscribers

Claude Desktop is Anthropic's native application for interacting with Claude AI models on macOS and Windows. It was the first consumer application to ship with built-in MCP support, making it the reference implementation for the Model Context Protocol standard.

Ask AI about this MCP Server for Claude Desktop

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

ClaudeClaude
ChatGPTChatGPT
CursorCursor
GeminiGemini
WindsurfWindsurf
VS CodeVS Code
JetBrainsJetBrains
VercelVercel
+ other MCP clients
Classic Setup·json
{
  "mcpServers": {
    "cubedev": {
      // Your Vinkius token. get it at cloud.vinkius.com
      "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.

Vinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop Interface
Download Free Open SourceNo signup required
Cube.dev
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.

Claude Desktop is the definitive way to connect Cube.dev to your AI workflow. Add Vinkius Edge URL to your config, restart the app, and Claude immediately exposes all 15 tools in the chat interface. ask a question, Claude calls the right tool, and you see the answer. Zero code, zero context switching.

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.

The Cube.dev MCP Server exposes 15 tools through the Vinkius. Connect it to Claude Desktop in under two minutes — credentials fully managed, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

All 15 Cube.dev tools available for Claude Desktop

When Claude Desktop connects to Cube.dev through Vinkius, your AI agent gets direct access to every tool listed below — spanning semantic-layer, data-modeling, sql-api, and more. Every call runs in a secure, isolated environment with full audit visibility. Beyond a simple connection, you get real-time monitoring of agent activity, enterprise governance, and optimized token usage.

check

Check live on Cube.dev

Check if Cube deployment is live

check

Check ready on Cube.dev

Check if Cube deployment is ready

convert

Convert query on Cube.dev

Convert a SQL query to a REST API query format

execute

Execute cube sql on Cube.dev

Execute a raw SQL query against the SQL API

generate

Generate meta token on Cube.dev

Requires CUBE_CLOUD_API_KEY. Generate a JWT for the Metadata API

get

Get entity on Cube.dev

Get detailed metadata for a specific entity

get

Get meta on Cube.dev

Get metadata for cubes and views

get

Get pre aggregation job status on Cube.dev

Get status of pre-aggregation jobs

get

Get sql on Cube.dev

Useful for debugging. Get generated SQL for a Cube query

list

List data sources on Cube.dev

List configured data sources

list

List deployments on Cube.dev

Requires CUBE_CLOUD_API_KEY. List all Cube Cloud deployments

list

List entities on Cube.dev

List all cubes and views

list

List environments on Cube.dev

Requires CUBE_CLOUD_API_KEY. List environments for a deployment

load

Load query on Cube.dev

Use this to get aggregated data. Execute a Cube query and return results

trigger

Trigger pre aggregation job on Cube.dev

Trigger a pre-aggregation build job

Connect Cube.dev to Claude Desktop via MCP

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

01

Open Claude Desktop Settings

Go to Settings → Developer → Edit Config to open claude_desktop_config.json
02

Add the MCP Server

Paste the configuration above into the mcpServers section
03

Restart Claude Desktop

Close and reopen Claude Desktop to load the new server
04

Start using Cube.dev

Look for the 🔌 icon in the chat. your 15 tools are now available

Why Use Claude Desktop with the Cube.dev MCP Server

Claude Desktop by Anthropic provides unique advantages when paired with Cube.dev through the Model Context Protocol.

01

Claude Desktop is the reference MCP client. it was designed alongside the protocol itself, ensuring the most complete and stable MCP implementation available

02

Zero-code configuration: add a server URL to a JSON file and Claude instantly discovers and exposes all available tools in the chat interface

03

Claude's extended thinking capability lets it reason through multi-step tool usage, chaining multiple API calls to answer complex questions

04

Enterprise-grade security with local config storage. your tokens never leave your machine, and connections go directly to Vinkius Edge network

Cube.dev + Claude Desktop Use Cases

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

01

Interactive data exploration: ask Claude to query DNS records, look up WHOIS data, and cross-reference results in a single conversation

02

Ad-hoc security audits: type a domain name and let Claude enumerate subdomains, check DNS history, and flag configuration anomalies. all through natural language

03

Executive briefings: generate comprehensive domain intelligence reports by asking Claude to compile findings into a formatted summary

04

Learning and training: new team members can explore API capabilities conversationally without needing to read documentation

Example Prompts for Cube.dev in Claude Desktop

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

01

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

02

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

03

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

Troubleshooting Cube.dev MCP Server with Claude Desktop

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

01

Server not appearing after restart

Ensure the JSON is valid (no trailing commas). Check the file path: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\\Claude\\ (Windows).
02

Authentication error

Verify your Vinkius token is correct. Go to cloud.vinkius.com to regenerate it if needed.
03

Tools not showing in chat

Click the 🔌 icon at the bottom of the chat input. If it shows 0 tools, the server may still be connecting. wait a few seconds.

Cube.dev + Claude Desktop FAQ

Common questions about integrating Cube.dev MCP Server with Claude Desktop.

01

How does Claude Desktop discover MCP tools?

When Claude Desktop starts, it reads the claude_desktop_config.json file and connects to each configured MCP server. It calls the tools/list endpoint to fetch the schema for every available tool, then surfaces them as clickable options in the chat interface via the 🔌 icon.
02

What happens if the MCP server is temporarily unavailable?

Claude Desktop handles disconnections gracefully. if the server is unreachable at startup, the tools simply won't appear. Once the server becomes available again, restarting Claude Desktop will re-establish the connection. There is no timeout penalty or error loop.
03

Can I connect multiple MCP servers simultaneously?

Yes. You can add as many servers as you need in the mcpServers section of the config file. Each server appears as a separate tool provider, and Claude can use tools from multiple servers in a single conversation turn.
04

Is there a limit on the number of tools per server?

Claude Desktop can handle hundreds of tools per server. However, for optimal LLM performance, Vinkius servers are designed to expose focused, well-documented tool sets rather than overwhelming the model with too many options.
05

Does Claude Desktop support Streamable HTTP transport?

Yes. Claude Desktop supports both SSE (Server-Sent Events) and the newer Streamable HTTP transport that Vinkius uses. Simply provide the server URL. Claude auto-negotiates the transport protocol.

Explore More MCP Servers

View all →