Skip to main content
Glama
wtkid

mcp-clickhouse-multids

by wtkid
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to mcp-clickhouse-multids

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.
      58 npm
      MIT

    • clickhouse-mcp

      stackblaze
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables SQL query execution on ClickHouse databases with per-request connection switching via HTTP headers, supporting multi-tenant deployments.
      Apache 2.0

    • Multi-DB MCP Server

      1249zts
      F
      license
      Not graded
      quality
      D
      maintenance
      A multi-database MCP server supporting PostgreSQL, ClickHouse, and MySQL that enables database exploration and SQL execution through MCP stdio or HTTP API.
      -

    • MCP Universal DB Client

      IzumiSy
      A
      license
      A
      quality
      C
      maintenance
      Enables connecting to and querying multiple database types (PostgreSQL, MySQL, SQLite) through a unified interface. Supports managing multiple concurrent database connections with connection pooling and SQL query execution through MCP tools.
      5
      11 npm
      MIT

    • 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

    C2.2/5.0

    Scored across 6 tools

    Disambiguation4/5

    Tool names like 'list_registered_datasources' and 'list_databases' suggest distinct purposes, but missing descriptions for most tools could cause ambiguity for an agent, especially between datasource and database/tables listing. However, the naming is sufficiently clear to differentiate them.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern in snake_case (e.g., list_registered_datasources, register_datasource, run_query). No mixing of styles or conventions.

    Tool Count5/5

    With 6 tools covering datasource management, database/table listing, and query execution, the count is well within the ideal range (3-15) for a focused multi-datasource ClickHouse server.

    Completeness3/5

    The tool set covers basic CRUD for datasources (list, register, unregister) and read operations (list databases/tables, run query). Missing update datasource and write operations (though run_query can be configured for writes). Notable gaps for a full lifecycle.

    Maintenance

    ActivityMaintained
    ResponsivenessSyncing

    Resources