Skip to main content
Glama
jvanvalkenhoef

clickhouse-mcp

by jvanvalkenhoef
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to clickhouse-mcp

No user-submitted related servers found.

    Related Servers

    • clickhouse-readonly-mcp

      MP-Trade
      F
      license
      Not graded
      quality
      C
      maintenance
      Minimal MCP server for read-only access to ClickHouse, enabling AI agents to explore schemas and execute SELECT queries safely.
      -
    • Altinity MCP by Altinity

      Altinity MCPofficial

      Altinity
      F
      license
      Not graded
      quality
      A
      maintenance
      Production-ready MCP server designed to empower AI agents and LLMs to interact seamlessly with ClickHouse. It exposes your ClickHouse database as a set of standardized tools and resources that adhere to the MCP protocol, making it easy for agents built on OpenAI, Claude, or other platforms to query, explore, and analyse your data.
      37
      -

    • mcp-clickhousex

      alyiox
      A
      license
      A
      quality
      B
      maintenance
      A read-only MCP server for ClickHouse that enables metadata discovery, parameterized SELECT queries, SHOW introspection, query analysis, and snapshot mode for large result sets, with profile-based configuration and strict no-DML/DDL enforcement.
      8
      MIT

    • db-connect-mcp

      yugui923
      A
      license
      A
      quality
      A
      maintenance
      A read-only MCP server for exploratory data analysis across PostgreSQL, MySQL, and ClickHouse databases, providing safe, read-only access with comprehensive analysis capabilities.
      10
      70 PyPI
      6
      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

    A4/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool targets a distinct operation: listing databases, listing tables, sampling rows, describing columns, showing the CREATE statement, and running arbitrary queries. While describe_table and show_create_table both expose schema information, their purposes are clearly separated by level of detail and use case. No two tools are likely to be confused.

    Naming Consistency4/5

    The tool names mostly follow a consistent verb_noun pattern (list_databases, list_tables, describe_table, show_create_table, sample_rows). The exception is 'query', which is a single verb, but it is a reasonable outlier given its generic nature. Overall, the naming is predictable and easy to navigate.

    Tool Count5/5

    Six tools is an ideal size for a ClickHouse exploration server, covering all essential read-only operations without unnecessary bloat. Each tool has a clear purpose and none feel redundant. The count is well-scoped for the server's stated goal of investigating telemetry data.

    Completeness5/5

    The tool set provides full coverage for the core workflows: discovering databases and tables, understanding table schemas via describe and CREATE statements, sampling data, and running arbitrary queries for deeper analysis. There are no obvious gaps for a read-only data exploration server; any additional needs can be fulfilled through the query tool.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources