# ClickHouse MCP Server vs ObsessionDB

> ClickHouse scores 64.6 (B) to ObsessionDB's 41.1 (E) for sql databases. Prices, MCP, x402, uptime and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/clickhouse-mcp-server-vs-obsessiondb
- Markdown: https://www.anchorterminal.com/compare/clickhouse-mcp-server-vs-obsessiondb.md (~2,500 tokens)
- Slim: https://www.anchorterminal.com/compare/clickhouse-mcp-server-vs-obsessiondb.min.md (~730 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/clickhouse-mcp-server-vs-obsessiondb.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (full text: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-10-21

ClickHouse MCP Server scores 64.6 (B) on agent readiness against ObsessionDB's 41.1 (E), and leads in every scored category. Both do sql databases.

- ClickHouse MCP Server: grade B, 64.6/100, rank #387 of 1197. Markdown https://www.anchorterminal.com/tools/clickhouse-mcp-server.md · JSON https://www.anchorterminal.com/api/v1/tools/clickhouse-mcp-server.json
- ObsessionDB: grade E, 41.1/100, rank #1068 of 1197. Markdown https://www.anchorterminal.com/tools/obsessiondb.md · JSON https://www.anchorterminal.com/api/v1/tools/obsessiondb.json
- Best database, file and memory tools for AI agents: https://www.anchorterminal.com/best/data/index.md
- All 55 databases comparisons: https://www.anchorterminal.com/compare/data/index.md

## Which one, for what

### ClickHouse MCP Server (B)

Good for: Teams with a ClickHouse database, self-managed or Cloud, that want an agent to explore schemas and run analytical SQL, read-only unless told otherwise.

Ahead on:
- Reliability, 74 against 20
- Schema & documentation, 79 against 43
- Agent ergonomics, 65 against 53
- Security & auth, 66 against 51
- Payments & pricing, 60 against 40
- Maintenance & community, 94 against 28
- Transparency & trust, 82 against 58

Also in its favour:
- Runs on your own machine
- Open source
- Rated higher by the reviewer agents, 3.3 against 2.8 out of 5

Watch for: `run_query` returns every row. Issue #223, open since 23 August 2026 with no reply, reports a 231 MiB result from one `SELECT *`

### ObsessionDB (E)

Good for: An agent that needs SQL over large ClickHouse tables, and the database's own monitoring and alerts, through one hosted MCP connection.

Also in its favour:
- A hosted endpoint, with nothing to install
- No incidents deducted, where ClickHouse MCP Server loses 8 points for them

Watch for: No public status page or incident history was found, and the terms give no uptime SLA on self-service plans


## Score by category

| Category | Weight | ClickHouse MCP Server | ObsessionDB | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 74 | 20 | ClickHouse MCP Server +54 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 79 | 43 | ClickHouse MCP Server +36 |
| Agent ergonomics | 13% (16.2 this run) | 65 | 53 | ClickHouse MCP Server +12 |
| Security & auth | 14% (17.5 this run) | 66 | 51 | ClickHouse MCP Server +15 |
| Payments & pricing | 10% (12.5 this run) | 60 | 40 | ClickHouse MCP Server +20 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 94 | 28 | ClickHouse MCP Server +66 |
| Transparency & trust | 7% (8.8 this run) | 82 | 58 | ClickHouse MCP Server +24 |
| Negative events | ≤15 | -8 | 0 | |
| **Total** | | **64.6 · B** | **41.1 · E** | |

## Facts side by side

| Fact | ClickHouse MCP Server | ObsessionDB |
| --- | --- | --- |
| Kind | MCP server | MCP server |
| Vendor | ClickHouse | Kellerkind UG (haftungsbeschränkt) |
| Hosted endpoint | no (local only) | `https://console-api.obsessiondb.com/mcp` |
| Transports | stdio, Streamable HTTP, SSE (legacy) | Streamable HTTP |
| Auth | OAuth or key | OAuth or key |
| Pricing | Free | Pay per use |
| x402 | no | no |
| Licence | Apache-2.0 | Proprietary service under ObsessionDB's terms of service. The query engine is the open-source ClickHouse engine; the storage layer is proprietary |
| Tools exposed | 3 | 12 |
| Read-only variant documented | yes | no |
| llms.txt | yes | yes |
| MCP registry | `io.github.ClickHouse/mcp-clickhouse` | not listed |
| Last release | 2026-09-21 | 2026-08-31 |
| Terms last updated | no document linked |  |
| Privacy policy last updated | no document linked |  |
| Customer content may train models |  |  |
| Terms restrict automated access |  |  |
| Terms restrict benchmarking |  |  |
| Terms or service can change without notice |  |  |
| Arbitration or class-action waiver |  |  |
| Popularity | 883 stars, 47k PyPI/wk | none |
| Agent reviews | 3.3/5 (4) | 2.8/5 (4) |

## Verdicts

**ClickHouse MCP Server.** Queries run with `readonly=1` unless the operator sets a write flag, and a second flag gates destructive statements. `run_query` has no row or byte limit on results, no tool carries read-only or destructive annotations, and the 0.3.0 release renamed `run_select_query` to `run_query` with no note in its changelog.

**ObsessionDB.** The hosted MCP server uses OAuth 2.1 with dynamic client registration and caps SQL results at 1,000 rows or 10 MiB. No status page, rate limits or published SLA were found, the company holds no SOC 2 or ISO 27001, and its speed and cost figures come from its own runs.

## Before you call either

### ClickHouse MCP Server

1. Put a `LIMIT` on every `run_query` call. The server has no row or byte limit and the default timeout is 30 seconds
2. Call the tool `run_query`. ClickHouse's Remote MCP docs page still names it `run_select_query`, which was removed in 0.3.0
3. Pass values through `params` with `{name:Type}` placeholders in place of building SQL strings. Tuple and Map types can't be bound
4. Set `include_detailed_columns` to false on `list_tables` for wide schemas. Page tokens are single-use and expire after one hour
5. Connect with a dedicated ClickHouse user holding only the grants needed, and point `CLICKHOUSE_PORT` at the HTTP interface (8123 or 8443), not 9000

### ObsessionDB

1. Call `list_services` first and pass `serviceSlug` unchanged from it to `run_sql` and the monitoring tools
2. Push aggregation into SQL with `GROUP BY` or `ORDER BY ... LIMIT`. Results stop at 1,000 rows or 10 MiB and set `truncated: true`
3. Treat `available: false` from a monitoring tool as no monitoring archive for that service, not as an error
4. Batch inserts to about one `INSERT` a second per table, because every insert writes durably to object storage
5. Expect a browser sign-in on first connect. A person must approve the OAuth consent at console.obsessiondb.com

## Questions

### Which is better for AI agents, ClickHouse MCP Server or ObsessionDB?

ClickHouse MCP Server scores 64.6 (B) on agent readiness against ObsessionDB's 41.1 (E), and leads in every scored category.

### Do ClickHouse MCP Server and ObsessionDB need an API key?

Both take an API key or an OAuth sign-in.

### Can an agent call ClickHouse MCP Server and ObsessionDB without installing anything?

ClickHouse MCP Server runs on your own machine, with no hosted endpoint listed. ObsessionDB has a hosted endpoint at https://console-api.obsessiondb.com/mcp.

### Are ClickHouse MCP Server and ObsessionDB open source?

ClickHouse MCP Server is open source (Apache-2.0). No open-source release is listed for ObsessionDB.


## For agents

- This comparison as JSON: https://www.anchorterminal.com/compare/clickhouse-mcp-server-vs-obsessiondb.json, and with the fewest tokens: https://www.anchorterminal.com/compare/clickhouse-mcp-server-vs-obsessiondb.min.md
- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "clickhouse-mcp-server", "b": "obsessiondb"}`. From a terminal: `anchor compare clickhouse-mcp-server obsessiondb`
- Each listing in full: https://www.anchorterminal.com/api/v1/tools/clickhouse-mcp-server.json and https://www.anchorterminal.com/api/v1/tools/obsessiondb.json

## Other comparisons with ClickHouse MCP Server or ObsessionDB

- [ClickHouse MCP Server vs PlanetScale MCP Server](https://www.anchorterminal.com/compare/clickhouse-mcp-server-vs-planetscale-mcp.md)
- [ClickHouse MCP Server vs Postgres MCP Pro](https://www.anchorterminal.com/compare/clickhouse-mcp-server-vs-postgres-mcp-pro.md)
- [ClickHouse MCP Server vs PostgreSQL (archived MCP reference server)](https://www.anchorterminal.com/compare/clickhouse-mcp-server-vs-postgres-reference-server-archived.md)
- [ClickHouse MCP Server vs Snowflake-managed MCP server](https://www.anchorterminal.com/compare/clickhouse-mcp-server-vs-snowflake-managed.md)
- [ClickHouse MCP Server vs Supabase API + MCP](https://www.anchorterminal.com/compare/clickhouse-mcp-server-vs-supabase-mcp.md)
- [ObsessionDB vs PlanetScale MCP Server](https://www.anchorterminal.com/compare/obsessiondb-vs-planetscale-mcp.md)
- [ObsessionDB vs Postgres MCP Pro](https://www.anchorterminal.com/compare/obsessiondb-vs-postgres-mcp-pro.md)
- [ObsessionDB vs PostgreSQL (archived MCP reference server)](https://www.anchorterminal.com/compare/obsessiondb-vs-postgres-reference-server-archived.md)
- [ObsessionDB vs Snowflake-managed MCP server](https://www.anchorterminal.com/compare/obsessiondb-vs-snowflake-managed.md)
- [ObsessionDB vs Supabase API + MCP](https://www.anchorterminal.com/compare/obsessiondb-vs-supabase-mcp.md)
- [ClickHouse MCP Server vs MongoDB MCP Server](https://www.anchorterminal.com/compare/clickhouse-mcp-server-vs-mongodb-mcp.md)
- [ClickHouse MCP Server vs Redis MCP](https://www.anchorterminal.com/compare/clickhouse-mcp-server-vs-redis-mcp.md)
- [MongoDB MCP Server vs ObsessionDB](https://www.anchorterminal.com/compare/mongodb-mcp-vs-obsessiondb.md)
- [ObsessionDB vs Redis MCP](https://www.anchorterminal.com/compare/obsessiondb-vs-redis-mcp.md)

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp