@mob999/cube_mcp
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@@mob999/cube_mcp list all available cubes and their measures"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Cube.js TypeScript MCP Server
This is a standalone Model Context Protocol (MCP) server for Cube.js, written in TypeScript using the official @cubejs-client/core SDK.
It provides advanced AI assistants (like Claude, Cursor, etc.) with semantic layer visibility and multi-dimensional querying capabilities over your data.
Features
discover_entities: Introspects the Cube.js metadata (/meta) and explains the available Cubes, Dimensions, and Measures to the LLM.execute_query: Executes semantic queries (/load) with support for Cube query fields like filters, sorting, time dimensions, pagination, timezone, and result truncation.
Related MCP server: Cube MCP Server
Prerequisites
Node.js (v18 or higher recommended)
A running instance of Cube.js
Quick Start
You can run the published MCP server directly without installing it manually:
npx -y @mob999/cube_mcpLocal Development & Build
Install dependencies:
npm installBuild the TypeScript source:
npm run buildThis compiles the TypeScript code into the
dist/directory.
Development & Testing
Run Tests:
npm testLint Code:
npm run lint
Query Features
execute_query supports:
measuresdimensionsfilterstimeDimensionssegmentslimitrowLimitoffsetordertimezonerenewQueryungroupedresponseFormattotal
Example:
{
"entity_name": "Components",
"measures": ["Components.count"],
"dimensions": ["Components.id"],
"timeDimensions": [
{
"dimension": "Components.createdAt",
"granularity": "day",
"dateRange": ["2026-01-01", "2026-01-31"]
}
],
"order": [
{ "member": "Components.count", "direction": "desc" },
{ "member": "Components.id", "direction": "asc" }
],
"limit": 100,
"rowLimit": 500,
"offset": 0,
"timezone": "UTC",
"responseFormat": "compact",
"total": true
}Configuration
By default, the server expects your Cube.js API to be available at http://localhost:4000/cubejs-api/v1.
You can override this by setting the CUBEJS_API_URL environment variable.
To integrate this semantic layer into Cursor or any other MCP-compatible IDE/Agent, configure it as a stdio tool.
Example mcp.json / Client Configuration:
{
"mcpServers": {
"CubeSemanticLayer": {
"command": "npx",
"args": ["-y", "@mob999/cube_mcp"],
"env": {
"CUBEJS_API_URL": "http://localhost:4000/cubejs-api/v1"
}
}
}
}Note: The -y flag allows npx to automatically download and run the package without prompting for confirmation.
Available Tools
2 toolsdiscover_entitiesA
Discover available Data Assets (Entities). Use this tool FIRST to understand the schema (Dimensions and Measures) available for querying. Returns a catalog of Semantic Entities with descriptions of their fields.
Inputs: no named parameters.
execute_queryA
Execute an Analytical Query. Perform multi-dimensional analysis on one of the entities discovered via 'discover_entities'.
Inputs: entity_name (required), limit, order, total, +11 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 2 tools
The two tools serve clearly different stages of the workflow: one discovers available entities/schema and the other executes queries against them. There is no overlap or ambiguity between them.
Both tool names follow the same verb_noun snake_case pattern: discover_entities and execute_query. The naming is consistent and conveys the action clearly.
Two tools is at the thin end of the range, but the pair forms a minimal coherent workflow for semantic analytics. The count feels slightly under-provisioned rather than excessive.
The core lifecycle of discovery-then-query is covered, allowing an agent to find entities and run analytical queries. Minor gaps exist, such as no dedicated metadata or validation tools, but they are not essential to the primary purpose.
Maintenance
Related MCP Connectors
Answer questions using your semantic layer and company knowledge graph.
Company and industrial data for AI assistants: datasets, SQL, dashboards, alarms, with approvals.
Build a semantic layer of reusable metrics and query it in plain words. Share models with your team.
Connect AI assistants to Preset to explore data, charts, and dashboards in authorized workspaces.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to query and analyze data from Cube.js analytics platforms, allowing natural language access to cubes, measures, dimensions, and complex analytics queries.9MIT
- AlicenseBqualityDmaintenanceEnables users to interact with Cube's AI agent for real-time analytics and data exploration through a chat interface. It supports generating data visualizations, performing SQL queries, and analyzing trends using natural language.113MIT
- FlicenseBqualityDmaintenanceAn MCP server that bridges AI assistants with data warehouses through Cube.js to enable governed, natural language semantic analytics queries. It provides tools for metadata discovery and secure query execution while enforcing governance policies like PII blocking and access limits.31-
- AlicenseCqualityDmaintenanceConnects databases to AI assistants, enabling natural language data analysis, cross-database queries, automated insights, and visualizations.461MIT