MCP Clickhouse vs Elasticsearch MCP Server
A side-by-side look at the MCP Clickhouse and Elasticsearch MCP Server MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose MCP Clickhouse for databases work as a local process; choose Elasticsearch MCP Server for databases as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose MCP Clickhouse when
- You need dedicated capabilities in the Databases domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: other.
- You want tools like
list_databases, list_tables, run_query.
Choose Elasticsearch MCP Server when
- You need dedicated capabilities in the Databases domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You want tools like
list_indices, get_index, create_index.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Databases | Databases |
| Quality signal | 67/100 · Great | 65/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | other | API key required |
| Pricing | Free | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 890 | 313 |
| Directory activity | 6 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | 3 | 20 |
| Full listing | View MCP Clickhouse | View Elasticsearch MCP Server |
Tools & capabilities
MCP Clickhouse tools 3
list_databasesList available ClickHouse databaseslist_tablesList available ClickHouse tables in a database, including schema, comment, row count, and column count. Integers outside [-9007199254740991, 9007199254740991] in table metadata are returned as decimal strings. Pagination tokens are single-use and retained for up to one hour.run_queryExecute SQL queries in ClickHouse. Queries run in read-only mode by default. Bind optional params by name with {name:Type} placeholders, such as {name:String} or {vector:Array(Float32)}. Values may be JSON scalars, nulls, or arrays. Pass exact large integers as decimal strings. JSON lists and objects cannot bind to Tuple and Map types. Python percent formatting and $name$ raw binary parameters are not supported. Parameter values stay out of the MCP server's normal SQL log lines, but may appear in errors and backend logs. Set CLICKHOUSE_ALLOW_WRITE_ACCESS=true to allow DDL and DML operations. Set CLICKHOUSE_ALLOW_DROP=true to additionally allow destructive operations (DROP, TRUNCATE, DELETE, UPDATE, REPLACE TABLE/PARTITION, CREATE OR REPLACE, CLEAR COLUMN/INDEX/PROJECTION, DETACH PERMANENTLY). That gate is a best-effort accident guard, not a security boundary. Integers outside [-9007199254740991, 9007199254740991] are returned as decimal strings. Two optional checks also run through this tool. Use DESCRIBE (<query>) when you need a query's output columns and types; it inspects the result schema and surfaces analysis errors such as an unknown column, but a query that describes cleanly can still fail at runtime. Consider EXPLAIN ESTIMATE <query> before a SELECT that could be expensive; it returns the estimated parts, rows and marks read from MergeTree family tables, which is not run time and not result size. Neither runs the query body, though analysis can execute scalar subqueries.
Elasticsearch MCP Server tools 20
list_indicesList all indices.get_indexReturns information (mappings, settings, aliases) about one or more indices.create_indexCreate a new index.delete_indexDelete an index.search_documentsSearch for documents.index_documentCreates or updates a document in the index.get_documentGet a document by ID.delete_documentDelete a document by ID.delete_by_queryDeletes documents matching the provided query.get_cluster_healthReturns basic information about the health of the cluster.get_cluster_statsReturns high-level overview of cluster statistics.list_aliasesList all aliases.- +8 more on the listing page
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
MCP Clickhouse
{
"mcpServers": {
"clickhouse-mcp-clickhouse": {
"command": "uvx",
"args": [
"mcp-clickhouse"
]
}
}
}
Elasticsearch MCP Server
{
"mcpServers": {
"cr7258-elasticsearch-mcp-server": {
"command": "uvx",
"args": [
"elasticsearch-mcp-server"
]
}
}
}
Frequently asked questions
MCP Clickhouse is categorized under Databases and uses a local stdio subprocess. Elasticsearch MCP Server belongs to Databases and uses a local stdio subprocess. Pick MCP Clickhouse for databases work and Elasticsearch MCP Server for databases.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
MCP Clickhouse is listed as free. Auth: other. Elasticsearch MCP Server is listed as free. Auth: api key required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add clickhouse-mcp-clickhouse and cr7258-elasticsearch-mcp-server as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, MCP Clickhouse has a quality signal of 67/100 (Great) with 6 views, 0 installs and 890 GitHub stars. Elasticsearch MCP Server has 65/100 (Great) with 3 views, 0 installs and 313 GitHub stars.