M
MCP Directory CURATED DIRECTORY
911 MCP servers indexed
中文
← Back to directory
COMPARE UP TO 4 SERVERS

Compare MCP servers

Compare scores, permissions, risks, and fit in one decision-focused table.

DimensionSLayerAn embeddable, expressive semantic layer for AI agents and humansMCP ClickHouseConnect ClickHouse to your AI assistants
FMRS48 / 100 · D79 / 100 · B
Reliability7 / 2012 / 20
Security and permissions9 / 2018 / 20
Maintenance10 / 2017 / 20
Documentation10 / 2017 / 20
Setup experience12 / 2015 / 20
Best for
  • Data teams wanting a governed data access surface for AI agents
  • Developers building analytical MCP servers or APIs on top of a warehouse
  • Teams with existing dbt, Cube, or Ossie semantic configs they want to reuse
  • Engineers embedding a semantic layer into Python apps
  • Teams already using ClickHouse who want AI assistants to access data directly.
  • Scenarios requiring fast, read-only data queries and schema exploration.
Not for
  • Scenarios requiring write access to the database (SLayer connections are read-only)
  • Simple cases where direct SQL is sufficient and no semantic layer is needed
  • Non-Python stacks that cannot run the CLI or an MCP subprocess
  • Scenarios requiring write access to the database without explicit opt-in.
  • Production environments with stringent security requirements that avoid default permission settings.
Required permissions
  • Read-only database access to configured datasources
  • Environment variables holding database credentials such as DB_PASSWORD
  • Permission to run the local CLI and the MCP subprocess
  • Permission to modify Claude Code MCP configuration
  • Requires read-only access to ClickHouse database (default).
  • Optional: write access via CLICKHOUSE_ALLOW_WRITE_ACCESS.
  • Optional: destructive operations via CLICKHOUSE_ALLOW_DROP.
Risks and side effects
  • Database credentials are passed to the MCP subprocess via environment variables, so a compromised launching shell could expose them
  • Connections are read-only but can still read sensitive business data, so row-level security should be applied
  • Once connected via MCP, agents can run queries, so verify their query scope matches expectations
  • As a third-party project, availability and behavior depend on upstream maintenance
  • If write access is enabled, AI might make unintended modifications.
  • If DROP access is enabled, data deletion could occur accidentally.
  • Credentials may be exposed via environment variables.
Supported clientsClaude CodeClaude Desktop
Tools04