Skip to main content
Glama
syucream

Lightdash MCP Server

by syucream
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Lightdash MCP Server

No user-submitted related servers found.

    Related Servers

    • Lightdash MCP Server

      poddubnyoleg
      A
      license
      A
      quality
      C
      maintenance
      A Model Context Protocol server for interacting with Lightdash, enabling AI assistants to discover data, create charts, and manage dashboards programmatically.
      28
      23
      MIT

    • metabase-mcp

      livingroot
      A
      license
      Not graded
      quality
      B
      maintenance
      A TypeScript/Node.js MCP server that wraps the Metabase REST API, enabling AI agents to execute queries, explore schemas, and build dashboards through structured tool calls.
      39 npm
      MIT

    • Semantic BI MCP

      LovroBubanic
      F
      license
      Not graded
      quality
      D
      maintenance
      Model Context Protocol (MCP) server that gives AI assistants a safe, correct data-analyst capability over business metrics - without raw SQL improvisation.
      -

    • superset-mcp

      thedeceptio
      F
      license
      B
      quality
      D
      maintenance
      An MCP server that provides AI assistants with full access to Apache Superset instances, enabling interaction with dashboards, charts, datasets, databases, and SQL execution capabilities.
      34
      -

    • mcp-superset

      chenwenyu1014
      A
      license
      Not graded
      quality
      C
      maintenance
      A comprehensive MCP server for Apache Superset. Gives AI assistants full control over your Superset instance — dashboards, charts, datasets, SQL Lab, users, roles, RLS, and more — through 137 tools.
      MIT

    • Metabase MCP Plus

      schachan
      A
      license
      A
      quality
      C
      maintenance
      An MCP server that enables AI assistants to query databases, execute SQL, and manage Metabase resources like dashboards, cards, and collections through natural language.
      22
      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

    B3.2/5.0

    Scored across 13 tools

    Disambiguation4/5

    Most tools target distinct resources (analytics, catalog, charts, dashboards, projects), but there is potential confusion between 'get_catalog' and 'get_metrics_catalog', and between 'get_analytics' and 'get_metadata' for a specific table. Descriptions help clarify, but some overlap exists.

    Naming Consistency5/5

    All tools follow a consistent 'lightdash_verb_noun' pattern, using 'get_' or 'list_' prefixes. The 'as_code' suffix in two tools is a minor deviation but still fits the pattern well.

    Tool Count5/5

    With 13 tools covering catalog, charts, dashboards, metrics, projects, spaces, and user attributes, the number is well-scoped for a read-only analytics server. It is neither too few nor too many.

    Completeness3/5

    The server covers many read operations (get, list) but lacks any write tools (create, update, delete), which is a notable gap for full lifecycle management in Lightdash. Agents may need write capabilities for many workflows.

    Maintenance

    ActivityInactive
    ResponsivenessUnresponsive

    Resources