Skip to main content
Glama
mob999

@mob999/cube_mcp

by mob999
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to @mob999/cube_mcp

No user-submitted related servers found.

    Related Servers

    • Cube.js MCP Server

      zsembek
      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

    • Cube MCP Server

      7BlockLabs
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to interact directly with Cube's API, allowing them to list cubes/views and metadata, run queries, and retrieve generated SQL.
      MIT
    • hq-demo by hypequery

      hq-demoofficial

      hypequery
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to interact with ClickHouse analytics through a semantic layer, exposing datasets and metrics for natural-language querying.
      -

    • Cube MCP Server

      cubedevinc
      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
      17 npm
      13
      MIT

    • DB-MCP

      scrappymonkey
      A
      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
      59 npm
      1
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    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

    ActivityInactive
    ResponsivenessNo issues

    Resources