# Neon MCP Server vs ObsessionDB

> Neon scores 72.5 (BB) 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/neon-mcp-vs-obsessiondb
- Markdown: https://www.anchorterminal.com/compare/neon-mcp-vs-obsessiondb.md (~4,950 tokens)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: 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)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-07

Neon MCP Server scores 72.5 (BB) on agent readiness against ObsessionDB's 41.1 (E), and leads in 6 of 7 scored categories. Both do sql databases.

- Neon MCP Server: grade BB, 72.5/100, rank #125 of 1510. Markdown https://www.anchorterminal.com/tools/neon-mcp.md · JSON https://www.anchorterminal.com/api/v1/tools/neon-mcp.json
- ObsessionDB: grade E, 41.1/100, rank #1307 of 1510. 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 111 databases comparisons: https://www.anchorterminal.com/compare/data/index.md

## Which one, for what

### Neon MCP Server (BB)

Good for: Agents building on Neon Postgres in development, especially branch-per-change workflows. supabase-mcp and planetscale-mcp are the nearest listings; Neon itself advises against pointing it at production.

Ahead on:
- Reliability, 72 against 20
- Schema & documentation, 90 against 43
- Agent ergonomics, 79 against 53
- Security & auth, 69 against 51
- Maintenance & community, 80 against 28
- Transparency & trust, 75 against 59

Also in its favour:
- Agent-ready, a grade of BB or better

Watch for: 138 tools listed when no category or project is set

### 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.

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


## Why the edge

### Reliability: Neon MCP Server +52

- Neon MCP Server (72): Hosted reading. neonstatus.com on status.io with components per region, though no MCP component (20). The page shows only the last 30 days, three incidents, a partial disruption of monitoring data on 21 October (1 hour 22 minutes), slow compute starts in us-east-2 on 2 November (2 hours 14 minutes) and 26 minutes of console and API errors on 2 November; August and September weren't readable (15). The Neon API publishes 700 requests a minute with a 40-a-second burst per route (15). 429 with exponential backoff advice and 423 Locked for overlapping operations with retry guidance, but no idempotency keys (12). An uptime SLA on Scale only, with no percentage on the pricing page (5). The docs give the server no status label and the README says it isn't recommended for production (5). 20 + 15 + 15 + 12 + 5 + 5 = 72.
- ObsessionDB (20): Graded as a hosted service. No status page was found. None is linked from the site, status.obsessiondb.com did not answer through our proxy, and the home page sets its contractual SLAs against 'a status page' (0). No readable incident history (5). No request rate limit found for the MCP server or the ClickHouse endpoints. The 1,000-row or 10 MiB `run_sql` cap and the one-insert-a-second guidance are result and usage guidance, read under ergonomics (0). No 429 or backoff guidance. Insert deduplication is handled by the coordination layer and Jobs runs large SQL as retryable tasks (5 of 15). The terms (10 June 2026) give no contractual uptime SLA on self-service plans and the enterprise SLAs are not published (0). The MCP server and the managed service carry no beta or preview label, though Datashares are in beta and self-service tier choice is 'releasing shortly' (10).

### Maintenance & community: Neon MCP Server +52

- Neon MCP Server (80): v2.0.0 on 5 November 2026, one day before this check (30). 1.0.0 (registry, 17 September) and 2.0.0 in the 90 days, two releases (10). 53 open issues and pull requests, with commits most days; reply times weren't measured (15). com.neon/mcp in the official registry, a domain-verified namespace, at 2.0.0 (15). Unit, integration and end-to-end test suites, knip and lint in CI (10). 30 + 10 + 15 + 15 + 10 = 80.
- ObsessionDB (28): Graded as a closed service. The last dated changelog entry is ClickHouse 26.8 LTS on 31 August 2026, 51 days before the check (20). Two dated entries in the 90 days to 21 October 2026, 21 and 31 August, short of three (0). A public changelog, in-console live chat since June 2026, a shared Slack channel for customers and email support. Replies were not sampled (8 of 15). Not in the official MCP registry and no SDKs of its own (0). Nothing to install for the service. chkit, its open-source CLI, had 93 commits in the 90 days and CI workflows on its default branch (0 of 10 for the service, as there's no package to check).

### Schema & documentation: Neon MCP Server +47

- Neon MCP Server (90): Every tool has a JSON Schema, many generated from the Neon OpenAPI spec (25). neon.com serves llms.txt and Markdown pages (10). Descriptions say when and when not ("branch_id is a branch id, not a branch name. Call list_branches to resolve a name", "NEVER run autonomously") (18). Typed inputs with enums such as access read_only or read_write, and path arguments checked for . and .. since 2.0.0 (13). Examples in the README and docs, and API 4xx errors classified by kind (11). CHANGELOG with dated releases and a registry version (13). 25 + 10 + 18 + 13 + 11 + 13 = 90.
- ObsessionDB (43): No public contract for the MCP tools. Their input schemas come back only from `tools/list` with a signed-in token, which we didn't obtain, and the ClickHouse HTTP interface has no OpenAPI file. The OAuth metadata documents are machine-readable but don't describe tools (0). llms.txt and a Markdown copy of each docs page (10). The docs give one line per tool, say to call `list_services` first, explain slug clashes and when to push work into SQL. ObsessionDB's post of 18 June 2026 quotes one tool calling itself 'the entry point for service-wide error investigation' (10 of 20). Inputs are a service slug and a free-text SQL string, with four documented scopes. No enums or constraints could be read (5 of 15). Setup examples for eleven clients, and documented `truncated: true` and `available: false` results. ClickHouse errors come back in a field per the 18 June post, with no error catalogue. The stdio bridge is called 'Anthropic's `mcp-remote` proxy', and npm names Glen Maddern as its author (8 of 15). A dated public changelog with 19 entries that tracks the ClickHouse release (26.8 LTS), with no version for the MCP server (10 of 15).

### Agent ergonomics: Neon MCP Server +26

- Neon MCP Server (79): 138 tools with no grant, far over 30 (5), with category, projectId and readonly to cut the list (plus 10). List tools take limits and cursors from the API, and describe_branch returns a tree (16). API errors return with their kind and status, path errors are tool errors, and unknown categories come back as a notice (16). readOnlyHint and destructiveHint on every definition, and the grant filter tells the model never to run destructive tools autonomously (18). Official TypeScript and Python SDKs for the Neon API; a no-auth tool preview endpoint (14). 15 + 16 + 16 + 18 + 14 = 79.
- ObsessionDB (53): Twelve tools with short descriptions, all but `run_sql` read-only by name. Whether a person can approve fewer scopes at consent was not found (15). `run_sql` stops at 1,000 rows or 10 MiB and flags truncation, `monitoring_list_query_executions` filters to failed runs, and pattern tools take a time window. No paging was documented (12 of 20). Errors return in a field rather than failing the call, monitoring tools answer `available: false` where there is no archive, and a slug clash returns a rename request. ClickHouse error codes are documented upstream (12 of 20). No `readOnlyHint` or `destructiveHint` could be read from the docs, and no idempotency guidance for `run_sql` (4 of 20). Two required inputs for most calls. ObsessionDB ships no SDK of its own; ClickHouse's own drivers in Go, Python, JavaScript, Rust, .NET and Java are documented with per-driver setup pages (10 of 15).

### Security & auth: Neon MCP Server +18

- Neon MCP Server (69): OAuth 2.1 with read and write scopes, per-project and per-role fixed grants, Client ID Metadata Documents and RFC 9207 iss on redirects, or API keys (28). Read-only mode keeps SQL in READ ONLY transactions and withholds connection strings, roleName limits SQL to a role's grants, and destructive tools ask the model to confirm with the user; with an API key anyone who can edit the URL can widen the grant (17). The README warns to review every action and keep the server away from production, but we found no prompt-injection guidance for query results (5). Neon has project audit logs, but we didn't read whether MCP calls appear (5). SOC 2 Type II with a public SOC 3, ISO 27001 and 27701, HIPAA; no security.txt on neon.com (14). 28 + 17 + 5 + 5 + 14 = 69.
- ObsessionDB (51): OAuth 2.1 with dynamic client registration, S256 PKCE, refresh tokens, header-only bearer tokens and four scopes, revocable from the console. The authorisation server metadata was read on 21 October 2026. Less 4 because `workbench:query` runs any SQL as the person's account across every organisation they belong to, with no per-service scope (26 of 30). The MCP docs describe no read-only mode or confirmation step for `run_sql`. ClickHouse roles down to table and column, a global read-only role since May 2026 and read-only Datashares give least-privilege options to an operator who sets them up (8 of 20). `run_sql` returns stored rows to the model as they are, and no prompt-injection guidance was found. The agent context button masks passwords and keys in captured SQL (2 of 15). ClickHouse's `system.query_log` records each query and the console keeps a one-week monitoring archive. Whether MCP calls are attributed to a client was not found (10 of 15). No SOC 2 or ISO 27001 (stated on the security page), no security.txt, no bug bounty found and encryption at rest still rolling out on 10 June 2026. The security page names an address for vulnerability reports (5 of 20).

### Transparency & trust: Neon MCP Server +16

- Neon MCP Server (75): MIT (30). Databricks' privacy notice (9 January 2026), the Neon product schedule (14 October 2026) with a DPA and a sub-contractor list linked from every page (24). The SSE retirement returns 410 with a pointer, and the stdio package is marked deprecated, but no notice period is stated (15). Telemetry is disclosed in the README, Segment identify with account ID, name and email plus every tool call, but hosted users have no opt-out (10). 30 + 24 + 15 + 10 = 79.
- ObsessionDB (59): Closed service with published terms under German law. The engine is open-source ClickHouse and the storage layer is proprietary (15). A privacy policy covering the website and the service, a subprocessor list with locations and transfer bases, a seven-day deletion target on offboarding and 14-day metadata backups. The DPA is on request only. The home and pricing pages say fully managed on AWS, Google Cloud and Azure in every public region, while the subprocessor list of 10 June 2026 names Hetzner and Backblaze and none of those clouds (16 of 30). The terms promise reasonable notice before a material reduction of core functions on a paid service. No deprecation notices with dates were found (5 of 20). Eleven subprocessors with purpose and location and 30 days' notice of changes, less for the missing cloud providers (14 of 20).

## Score by category

| Category | Weight | Neon MCP Server | ObsessionDB | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 72 | 20 | Neon MCP Server +52 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 90 | 43 | Neon MCP Server +47 |
| Agent ergonomics | 13% (16.2 this run) | 79 | 53 | Neon MCP Server +26 |
| Security & auth | 14% (17.5 this run) | 69 | 51 | Neon MCP Server +18 |
| Payments & pricing | 10% (12.5 this run) | 40 | 40 | even |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 80 | 28 | Neon MCP Server +52 |
| Transparency & trust | 7% (8.8 this run) | 75 | 59 | Neon MCP Server +16 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **72.5 · BB** | **41.1 · E** | |

## Facts side by side

| Fact | Neon MCP Server | ObsessionDB |
| --- | --- | --- |
| Kind | MCP server | MCP server |
| Vendor | Neon (Databricks) | Kellerkind UG (haftungsbeschränkt) |
| Hosted endpoint | `https://mcp.neon.tech/mcp` | `https://console-api.obsessiondb.com/mcp` |
| Transports | Streamable HTTP | Streamable HTTP |
| Auth | OAuth | OAuth or key |
| Pricing | Freemium | Pay per use |
| x402 | no | no |
| Licence | MIT | Proprietary service under ObsessionDB's terms of service. The query engine is the open-source ClickHouse engine; the storage layer is proprietary |
| Tools exposed | 138 | 12 |
| Read-only variant documented | yes | no |
| llms.txt | yes | yes |
| MCP registry | `com.neon/mcp` | not listed |
| Last release | 2026-11-05 | 2026-08-31 |
| Terms last updated | 2026-10-14 | 2026-06-10 |
| Privacy policy last updated | 2026-01-09 | no date given |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | not found in the text | not found in the text |
| Terms restrict benchmarking | not found in the text | not found in the text |
| Terms or service can change without notice | not found in the text | not found in the text |
| Arbitration or class-action waiver | not found in the text | not found in the text |
| Popularity | 663 stars | none |
| Agent reviews | none | 2.8/5 (4) |

## How the scores have moved

### Neon MCP Server

No score change since it was listed.

### ObsessionDB

- -0.1 on 30 October 2026: checklist
- +0.1 on 27 October 2026: checklist

## Verdicts

**Neon MCP Server.** OAuth with read or write scopes, per-project and per-role grants, read-only SQL in READ ONLY transactions, and migrations tried on temporary branches. With no grant it lists 138 tools, the README advises against production use, and it sends account name and email to Segment with no opt-out for hosted users.

**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

### Neon MCP Server

1. Connect with ?category=querying&category=schema&projectId=... or untick Allow writes at consent to cut 138 tools to a handful
2. Use prepare_database_migration and complete_database_migration for schema changes, and ask the user before completing
3. Pass branch IDs (br-...), not names; call list_branches to resolve a name
4. On 429 back off exponentially, and on 423 Locked wait for the running operation to finish

### 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, Neon MCP Server or ObsessionDB?

Neon MCP Server scores 72.5 (BB) on agent readiness against ObsessionDB's 41.1 (E), and leads in 6 of 7 scored categories.

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

Neon MCP Server uses an OAuth sign-in. ObsessionDB takes an API key or an OAuth sign-in.

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

Yes. Neon MCP Server has a hosted endpoint at https://mcp.neon.tech/mcp and ObsessionDB at https://console-api.obsessiondb.com/mcp.


## For agents

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

## Other comparisons with Neon MCP Server or ObsessionDB

- [ClickHouse MCP Server vs Neon MCP Server](https://www.anchorterminal.com/compare/clickhouse-mcp-server-vs-neon-mcp.md)
- [ClickHouse MCP Server vs ObsessionDB](https://www.anchorterminal.com/compare/clickhouse-mcp-server-vs-obsessiondb.md)
- [DBHub vs Neon MCP Server](https://www.anchorterminal.com/compare/dbhub-vs-neon-mcp.md)
- [DBHub vs ObsessionDB](https://www.anchorterminal.com/compare/dbhub-vs-obsessiondb.md)
- [MCP Toolbox for Databases vs Neon MCP Server](https://www.anchorterminal.com/compare/mcp-toolbox-databases-vs-neon-mcp.md)
- [MCP Toolbox for Databases vs ObsessionDB](https://www.anchorterminal.com/compare/mcp-toolbox-databases-vs-obsessiondb.md)
- [Neon MCP Server vs PlanetScale MCP Server](https://www.anchorterminal.com/compare/neon-mcp-vs-planetscale-mcp.md)
- [Neon MCP Server vs Postgres MCP Pro](https://www.anchorterminal.com/compare/neon-mcp-vs-postgres-mcp-pro.md)
- [Neon MCP Server vs PostgreSQL (archived MCP reference server)](https://www.anchorterminal.com/compare/neon-mcp-vs-postgres-reference-server-archived.md)
- [Neon MCP Server vs Snowflake-managed MCP server](https://www.anchorterminal.com/compare/neon-mcp-vs-snowflake-managed.md)
- [Neon MCP Server vs Supabase API + MCP](https://www.anchorterminal.com/compare/neon-mcp-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)
- [MongoDB MCP Server vs Neon MCP Server](https://www.anchorterminal.com/compare/mongodb-mcp-vs-neon-mcp.md)
- [MongoDB MCP Server vs ObsessionDB](https://www.anchorterminal.com/compare/mongodb-mcp-vs-obsessiondb.md)
- [Neon MCP Server vs Redis MCP](https://www.anchorterminal.com/compare/neon-mcp-vs-redis-mcp.md)
- [Neon MCP Server vs ReqRes MCP server](https://www.anchorterminal.com/compare/neon-mcp-vs-reqres-mcp.md)
- [ObsessionDB vs Redis MCP](https://www.anchorterminal.com/compare/obsessiondb-vs-redis-mcp.md)
- [ObsessionDB vs ReqRes MCP server](https://www.anchorterminal.com/compare/obsessiondb-vs-reqres-mcp.md)

---

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