"clickhouse" matching MCP servers:

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.

Enables MCP clients to explore ClickHouse schemas, run analytical queries, and manage the database with statement-aware security modes and access-control flags.

Tracks a user's activity by trace ID from application logs stored in ClickHouse. Provides tools for log timeline, trace summaries, and search across services.

Read-only MCP server for querying ClickHouse (product telemetry) and Elasticsearch (download analytics), built for Percona VISTA.

Enables AI assistants to query Grafana datasources (Prometheus/Loki metrics and SQL databases like ClickHouse/Postgres/MySQL) and search or inspect dashboards through natural language, using read-only access to Grafana's API.

Enables MCP-capable AI clients to search ClickHouse logs, browse instances, databases, and tables, and inspect log histograms directly from a chat.

Enables read-only access to Percona Monitoring and Management 2.x through PromQL metric queries and Query Analytics, so clients can list monitored databases, surface the slowest queries, inspect query details, and run validated SELECT queries against QAN's ClickHouse data. TLS verification, input validation, and Viewer-role tokens keep access strictly observational.

Ranks log patterns by volume and cost on Splunk, Datadog, Elasticsearch, CloudWatch and ClickHouse, and plans compact, tier down or offload for the excess over each cap. Runs locally over stdio; no log data reaches log10x. Read-only against a public demo dataset without an API key.