Skip to main content
Glama
yeongbin-hwang

imply-druid-mcp

by yeongbin-hwang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to imply-druid-mcp

No user-submitted related servers found.

    Related Servers

    • sqldb-mcp-server

      akrym1582
      A
      license
      A
      quality
      C
      maintenance
      A read-only MCP server that exposes SQL database access to LLMs, supporting multiple database types, compact columnar results, pagination, and file export.
      6
      12 npm
      MIT

    • starrocks-mcp

      jason-ung
      A
      license
      A
      quality
      D
      maintenance
      A read-only MCP server that enables users to query and explore StarRocks databases through AI assistants like Claude. It supports SQL execution, schema discovery, and secure LDAP authentication for data analysis and metadata exploration.
      4
      1
      MIT

    • clickhouse-mcp

      jvanvalkenhoef
      A
      license
      A
      quality
      C
      maintenance
      A read-only MCP server for ClickHouse that enables AI agents to discover schema, sample data, and run read-only SQL queries to investigate observability data like logs, metrics, and traces.
      6
      6 npm
      MIT

    • mcp-sqlserver

      kyle66889
      A
      license
      Not graded
      quality
      C
      maintenance
      A read-only MCP server for Microsoft SQL Server that enables AI agents to safely explore and query SQL Server databases.
      623 npm
      MIT

    • TDengine Query MCP Server

      Abeautifulsnow
      A
      license
      B
      quality
      C
      maintenance
      A Model Context Protocol (MCP) server that provides read-only TDengine database queries for AI assistants, allowing users to execute queries, explore database structures, and investigate data directly from AI-powered tools.
      6
      11
      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.8/5.0

    Scored across 12 tools

    Disambiguation5/5

    Each tool has a clear, distinct purpose. Sync and async queries are separated, and the data cube query uses a different syntax. No two tools appear to do the same thing.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern (e.g., list_*, get_*, execute_*, cancel_*, query_*). No mixing of conventions or vague verbs.

    Tool Count5/5

    12 tools appropriately cover the core functionalities of querying Druid, managing dashboards, data cubes, and tables. Not too few nor too many.

    Completeness5/5

    The tool set provides full lifecycle coverage for querying (sync, async, cancellation, status, results) and browsing resources (list, get details, schema). No obvious gaps for a query-oriented server.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources