Skip to main content
Glama
dockndevai

mcp-clickhouse

by dockndevai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to mcp-clickhouse

No user-submitted related servers found.

    Related Servers

    • clickhouse-mcp-server

      ahmedrowaihi
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables interaction with ClickHouse databases via MCP, providing tools to list databases and tables and execute safe SELECT, SHOW, and DESCRIBE queries.
      77 npm
      MIT

    • mcp_db

      seraved
      F
      license
      Not graded
      quality
      D
      maintenance
      MCP server for executing SQL queries on PostgreSQL and ClickHouse with per-connection allow/deny policies by statement group.
      -

    • mcp-clickhousex

      alyiox
      A
      license
      A
      quality
      B
      maintenance
      A read-only-by-default Model Context Protocol (MCP) server for ClickHouse with schema discovery, parameterized SELECT-only queries, execution-plan analysis, and opt-in writes per profile. Profile-based configuration serves multiple clusters from one toolset deployment.
      8
      MIT

    • mcp-clickhouse-multids

      wtkid
      A
      license
      C
      quality
      C
      maintenance
      Enables connecting to multiple ClickHouse instances via dynamic registration or YAML configuration, supporting SQL queries and data source management through MCP tools.
      6
      Apache 2.0

    • clickhouse-mcp-server

      burakdirin
      A
      license
      B
      quality
      D
      maintenance
      An MCP server implementation that enables Claude AI to interact with Clickhouse databases. Features include secure database connections, query execution, read-only mode support, and multi-query capabilities.
      2
      2
      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.6/5.0

    Scored across 9 tools

    Disambiguation4/5

    Each tool targets a fairly distinct area: table listing, column metadata, DDL, stats, and system introspection. The main overlap is that `query` can also run SHOW/DESCRIBE and thus partially duplicates `describe_table`, `show_create_table`, `list_databases`, and `list_tables`, though dedicated tools provide clearer structured output.

    Naming Consistency3/5

    All names are snake_case, but the conventions are mixed: verb_noun forms (`list_tables`, `describe_table`, `show_create_table`), noun phrases (`table_stats`, `cluster_info`, `running_queries`, `server_metrics`), and a lone verb (`query`). Readable but not a predictable pattern.

    Tool Count5/5

    Nine tools is well-scoped for a ClickHouse introspection and query server. Each tool has a clear place, and there is no obvious bloat or missing category within the read-oriented surface.

    Completeness3/5

    Read-side coverage is solid (databases, tables, schema, stats, queries, cluster, metrics). However, the `query` description explicitly says non-read statements must use an `execute` tool, which is absent, leaving writes/DDL as a dead end and creating an inconsistent tool surface.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive

    Resources