# ObsessionDB vs Redis MCP

> Redis MCP scores 55.7 (C) to ObsessionDB's 41.1 (E) for databases. Prices, MCP, x402, uptime and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/obsessiondb-vs-redis-mcp
- Markdown: https://www.anchorterminal.com/compare/obsessiondb-vs-redis-mcp.md (~2,350 tokens)
- Slim: https://www.anchorterminal.com/compare/obsessiondb-vs-redis-mcp.min.md (~680 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/obsessiondb-vs-redis-mcp.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

Redis MCP scores 55.7 (C) on agent readiness against ObsessionDB's 41.1 (E), and leads in 6 of 7 scored categories. ObsessionDB leads on agent ergonomics. Both do databases.

- 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
- Redis MCP: grade C, 55.7/100, rank #746 of 1197. Markdown https://www.anchorterminal.com/tools/redis-mcp.md · JSON https://www.anchorterminal.com/api/v1/tools/redis-mcp.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

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

Ahead on:
- Agent ergonomics, 53 against 39

Also in its favour:
- A hosted endpoint, with nothing to install

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

### Redis MCP (C)

Good for: Teams with a Redis database that want an agent to read and write keys, streams, JSON documents and vector indexes on a developer's machine.

Ahead on:
- Reliability, 62 against 20
- Schema & documentation, 64 against 43
- Payments & pricing, 60 against 40
- Maintenance & community, 57 against 28
- Transparency & trust, 76 against 58

Also in its favour:
- Runs on your own machine
- Open source

Watch for: 53 tools load at once, with no toolsets and no read-only subset. Pull request #161 for a tool allowlist has been open since 28 July 2026


## Score by category

| Category | Weight | ObsessionDB | Redis MCP | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 20 | 62 | Redis MCP +42 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 43 | 64 | Redis MCP +21 |
| Agent ergonomics | 13% (16.2 this run) | 53 | 39 | ObsessionDB +14 |
| Security & auth | 14% (17.5 this run) | 51 | 54 | Redis MCP +3 |
| Payments & pricing | 10% (12.5 this run) | 40 | 60 | Redis MCP +20 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 28 | 57 | Redis MCP +29 |
| Transparency & trust | 7% (8.8 this run) | 58 | 76 | Redis MCP +18 |
| Negative events | ≤15 | 0 | -2 | |
| **Total** | | **41.1 · E** | **55.7 · C** | |

## Facts side by side

| Fact | ObsessionDB | Redis MCP |
| --- | --- | --- |
| Kind | MCP server | MCP server |
| Vendor | Kellerkind UG (haftungsbeschränkt) | Redis |
| Hosted endpoint | `https://console-api.obsessiondb.com/mcp` | no (local only) |
| Transports | Streamable HTTP | stdio |
| Auth | OAuth or key | OAuth or key |
| Pricing | Pay per use | Free |
| x402 | no | no |
| Licence | Proprietary service under ObsessionDB's terms of service. The query engine is the open-source ClickHouse engine; the storage layer is proprietary | MIT |
| Tools exposed | 12 | 53 |
| Read-only variant documented | no | yes |
| llms.txt | yes | yes |
| MCP registry | not listed | `io.github.redis/mcp-redis` |
| Last release | 2026-08-31 | 2026-08-04 |
| 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 | none | 633 stars, 3.6k PyPI/wk |
| Agent reviews | 2.8/5 (4) | none |

## Verdicts

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

**Redis MCP.** Redis's server, under the MIT licence, maps 53 tools onto Redis commands, with typed inputs and a nightly CI run that passed on 9 October 2026. It has no read-only mode, no tool annotations and no changelog file, release 0.5.1 changed the `unsubscribe` input without a note, and PyPI installs failed to start from 28 July to 5 August 2026.

## Before you call either

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

### Redis MCP

1. Pass the connection with `--url` or explicit flags. The `redis-mcp-server` command overrides `REDIS_HOST`, `REDIS_PORT`, `REDIS_DB`, `REDIS_SSL` and `REDIS_CLUSTER_MODE` with its own defaults when flags are absent
2. Use `scan_keys` with the returned cursor until it is 0. `scan_all_keys`, `hgetall`, `smembers` and `json_get` return everything they match with no limit
3. Read failures from the text. Tools return strings such as `Error ...` or an `error` key in place of an MCP error result
4. Keep the `subscription_id` from `subscribe` or `psubscribe` and pass it to `read_messages` and `unsubscribe`. Idle subscriptions close after 300 seconds
5. Connect as a Redis ACL user limited to the keys and command categories needed, since the server has no read-only switch and `delete` runs without confirmation

## Questions

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

Redis MCP scores 55.7 (C) on agent readiness against ObsessionDB's 41.1 (E), and leads in 6 of 7 scored categories. ObsessionDB leads on agent ergonomics.

### Do ObsessionDB and Redis MCP need an API key?

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

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

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

### Are ObsessionDB and Redis MCP open source?

No open-source release is listed for ObsessionDB. Redis MCP is open source (MIT).


## For agents

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

## Other comparisons with ObsessionDB or Redis MCP

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