mcp-clickhouse-long-running

by cgrdavies

Overview Schema Source Related Servers Discussions Admin

Python

Remote

Related Servers

Alternatives to mcp-clickhouse-long-running

No user-submitted related servers found.

Related Servers

ClickHouse MCP Server
Databases Search
iskakaushik
A
license
D
quality
F
maintenance
An MCP server for ClickHouse.
Updated 2 years ago (2025-01-06 22:45 UTC)
3
3
Apache 2.0
io.github.Aguantar/clickhouse
Databases Monitoring
Aguantar
A
license
A
quality
D
maintenance
A DataOps-focused MCP server for ClickHouse that provides query optimization advice, pipeline latency analysis, and data quality monitoring, with read-only safety.
Updated 6 months ago (2026-03-19 03:49 UTC)
8
30 PyPI
MIT
mcp-clickhouse
Databases Observability
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.
Updated 5 days ago (2026-09-18 22:24 UTC)
9
248 npm
2
MIT
clickhouse-mcp-server
Databases Developer Tools
reiple
F
license
A
quality
C
maintenance
Read-only MCP server for ClickHouse that allows listing databases and tables, describing schemas, and running SELECT queries.
Updated 3 months ago (2026-07-07 15:08 UTC)
4
-
clickhouse-mcp-server
Databases Developer Tools
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.
Updated a year ago (2025-09-07 06:37 UTC)
58 npm
MIT
clickhouse-mcp
Finance Databases Data Platforms
kevinkda
A
license
A
quality
C
maintenance
Read-only MCP server for large-scale cross-sectional quant analysis of US stock market data (1.49 billion rows) using ClickHouse.
Updated 17 days ago (2026-09-07 00:15 UTC)
7
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

B3.2/5.0

Scored 2026-04-18 09:50 across 3 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: list_databases for database enumeration, list_tables for table metadata within a database, and run_select_query for executing queries. There is no overlap in functionality, making tool selection straightforward for an agent.

Naming Consistency5/5

All tools follow a consistent verb_noun naming pattern (list_databases, list_tables, run_select_query), using snake_case throughout. This predictability aids in understanding and usage without any deviations.

Tool Count3/5

With only 3 tools, the server feels thin for a database interaction scope, lacking operations like data manipulation (INSERT/UPDATE/DELETE), schema modification, or query execution beyond SELECT. While core functions are present, the count is borderline low for comprehensive database management.

Completeness2/5

The tool set is significantly incomplete for ClickHouse database operations, covering only listing and SELECT queries. Missing are essential CRUD operations (e.g., INSERT, UPDATE, DELETE), schema changes (CREATE/ALTER/DROP), and other query types (e.g., SHOW, DESCRIBE), which will likely cause agent failures in broader workflows.