Skip to main content
Glama
mrsnurk32

cfm-dwh-mcp

by mrsnurk32
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to cfm-dwh-mcp

No user-submitted related servers found.

    Related Servers

    • mcp-clickhouse

      dockndevai
      A
      license
      A
      quality
      A
      maintenance
      Enables MCP clients to explore ClickHouse schemas, run analytical queries, and manage the database with statement-aware security modes and access-control flags.
      9
      248 npm
      2
      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

    • 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.
      34 npm
      MIT

    • sql_tool

      ShadowOO7
      F
      license
      Not graded
      quality
      C
      maintenance
      Exposes a DuckDB-backed MCP server that lets an agent fetch a dataset's schema and run read-only SQL queries against it. All execution is filtered server-side, enforcing single-statement, read-only safety independent of the calling model's behavior.
      -
    • MCP DB Gateway by altsys

      MCP DB Gatewayofficial

      altsys
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides governed, read-only PostgreSQL access for AI agents via MCP. Enforces schema/table allowlists, query limits, and audit events.
      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 3 tools

    Disambiguation5/5

    ping, list_allowed_tables, and query_clickhouse have clearly distinct purposes: health check, table discovery, and query execution. There is no overlap that would cause an agent to misselect.

    Naming Consistency4/5

    All names are lowercase snake_case and verb-led, giving a consistent style. ping is a standalone verb rather than a verb_noun pair, but this is a minor and conventional deviation for a health check.

    Tool Count5/5

    Three tools is small but well-scoped for a read-only ClickHouse gateway: connectivity check, allowlist discovery, and query execution. Each tool has a necessary and distinct role.

    Completeness4/5

    The core read-only workflow is covered: verify connectivity, list allowed tables, and run parameterized queries. The main gap is schema or column introspection, since list_allowed_tables exposes table names but not their structure.

    Maintenance

    ActivityMaintained
    ResponsivenessResponsive

    Resources