Skip to main content
Glama
yuki9541134

Redash MCP Server

by yuki9541134
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Redash MCP Server

No user-submitted related servers found.

    Related Servers

    • Redash MCP Server

      jasonsmithj
      A
      license
      B
      quality
      B
      maintenance
      Enables interaction with Redash instances through a standardized interface, allowing users to execute SQL queries, manage data sources, and retrieve query results using natural language.
      4
      175 npm
      1
      MIT

    • metabase-server

      yespark
      F
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables AI assistants to interact with Metabase by providing access to dashboards, questions, and databases through the Metabase API. It allows users to list resources, execute existing cards, and run custom SQL queries to retrieve data through natural language.
      15 npm
      -

    • metabase-mcp

      voducdan
      A
      license
      A
      quality
      D
      maintenance
      Enables AI assistants to interact with Metabase for database operations, SQL queries, dashboard management, and analytics automation.
      28
      MIT

    • Metabase MCP Server

      CPR43
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to interact with Metabase analytics platform, allowing users to query databases, manage dashboards and cards, execute SQL queries, and access analytics data through natural language.
      29 npm
      1
      MIT

    • Apache Druid MCP Server

      AnilPuram
      A
      license
      A
      quality
      C
      maintenance
      Enables querying and managing Apache Druid datasources through natural language, including SQL queries, datasource exploration, and cluster connectivity testing.
      4
      5 npm
      2
      Apache 2.0
    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.1/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: execute_query_and_wait runs queries, get_data_source retrieves details for a specific source, and list_data_sources enumerates all sources. There is no overlap or ambiguity between these operations.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern (execute_query_and_wait, get_data_source, list_data_sources) with clear, descriptive names that align well with their functions.

    Tool Count2/5

    With only 3 tools, the server feels under-scoped for a Redash-like data querying and visualization platform. Key operations like creating/updating queries, managing dashboards, or fetching query results are missing, making the set too thin for typical agent workflows.

    Completeness2/5

    The tool surface is severely incomplete for a Redash server. While it covers basic data source listing and query execution, it lacks essential CRUD operations for queries, dashboards, and visualizations, as well as lifecycle management tools, which will likely cause agent failures in complex tasks.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources