ObsessionDB vs Redis MCP

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.

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