← Back to directory
COMPARE UP TO 4 SERVERS

Compare MCP servers

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

DimensionGreptimeDB MCP ServerQuery and analyze GreptimeDB metrics, logs, and traces via SQL, TQL, and RANGE queries.MCP ClickHouseConnect ClickHouse to your AI assistants
FMRS60 / 100 · C79 / 100 · B
Reliability10 / 2012 / 20
Security and permissions12 / 2018 / 20
Maintenance11 / 2017 / 20
Documentation14 / 2017 / 20
Setup experience13 / 2015 / 20
Best for
  • Developers working with time-series and observability data.
  • Teams needing natural language access to their database for query and analysis.
  • Users wanting to integrate AI-assisted data exploration within MCP clients.
  • Teams already using ClickHouse who want AI assistants to access data directly.
  • Scenarios requiring fast, read-only data queries and schema exploration.
Not for
  • Users who need write operations or DDL/DML (read-only by default; write mode only for local/test, extremely risky).
  • Users not using GreptimeDB.
  • Users who need direct database access without MCP integration.
  • 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 access to GreptimeDB for SQL, TQL, and RANGE queries.
  • Access to HTTP API (default port 4000) for pipeline and dashboard management.
  • Access to configured credentials via environment variables or CLI arguments.
  • Data masking is enabled by default to prevent sensitive column exposure.
  • 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
  • If write mode is enabled (disabled by default), AI could execute destructive SQL; never enable against production.
  • Queries may be expensive if complex or misused; restrict access and resources.
  • Providing secret environment variables over HTTP could increase exposure risk.
  • Database may be inaccessible due to network configuration or startup issues.
  • 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 DesktopClaude Desktop
Tools134