Skip to main content
Glama
@mob999/cube_mcp

@mob999/cube_mcp

by mob999

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_mcp

Local Development & Build

  1. Install dependencies:

    npm install
  2. Build the TypeScript source:

    npm run build

    This compiles the TypeScript code into the dist/ directory.

Development & Testing

  • Run Tests: npm test

  • Lint Code: npm run lint

Query Features

execute_query supports:

  • measures

  • dimensions

  • filters

  • timeDimensions

  • segments

  • limit

  • rowLimit

  • offset

  • order

  • timezone

  • renewQuery

  • ungrouped

  • responseFormat

  • total

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 tools
discover_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

    A3.9/5.0

    Scored across 2 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    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.

    Tool Count3/5

    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.

    Completeness4/5

    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

    ActivityNo data
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to query and analyze data from Cube.js analytics platforms, allowing natural language access to cubes, measures, dimensions, and complex analytics queries.
      9
      MIT
    • A
      license
      B
      quality
      D
      maintenance
      Enables 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.
      1
      13
      MIT
    • F
      license
      B
      quality
      D
      maintenance
      An 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.
      3
      1
      -