| FMRS | 59 / 100 · C | 74 / 100 · B |
|---|
| Reliability | 9 / 20 | 13 / 20 |
|---|
| Security and permissions | 11 / 20 | 13 / 20 |
|---|
| Maintenance | 12 / 20 | 16 / 20 |
|---|
| Documentation | 14 / 20 | 15 / 20 |
|---|
| Setup experience | 13 / 20 | 17 / 20 |
|---|
| Best for | - AI agents that need offline, low-latency, local memory.
- Developers who want to avoid LLM calls during memory storage and recall.
- Projects requiring persistent memory, knowledge graphs, or Hebbian learning.
- Teams using Zenoh, ROS2, or robotic mission memory.
| - Scenarios wanting the smallest possible tool count and lowest context-window overhead for database access
- Cases needing to grant non-technical teammates safe, read-only database access
|
|---|
| Not for | - Users seeking a hosted cloud memory service or built-in multi-tenant authorization.
- Applications expecting the server itself to perform LLM inference.
- MCP clients operating without an available local backend.
- Workflows that only need simple stateless text processing.
| - Scenarios needing database administration operations (creating indexes, altering schema) rather than just querying (DBHub is positioned as a query tool, not a DBA management tool)
|
|---|
| Required permissions | - Access to read and write Shodh-Memory's local memory data.
- Permission to launch the npm package and local MCP server over stdio.
- Network access to the address specified by SHODH_API_URL when using a remote backend.
- SHODH_API_KEY when authentication is enabled; this variable is secret.
- The tools can create, modify, and delete memories, todos, projects, reminders, and backups.
| - Requires a database connection string (DSN), which may contain sensitive credentials
- execute_sql can run arbitrary SQL (including writes) by default — must be constrained via read-only mode or the underlying database account's own permissions
|
|---|
| Risks and side effects | - Memories, todos, projects, and backups may contain sensitive information and persist locally.
- forget, delete, purge, and backup_restore can cause data loss or overwrite data.
- For remote deployments, the deployer must protect the API key and network exposure.
- SHODH_USER_ID is a logical memory namespace, not an authorization tenant.
- A local model is downloaded on first run, requiring local resources and model storage.
| - Under default settings, if the connected database account has write access, execute_sql could let the assistant perform an unintended write or delete — pair with a read-only database account in production
- The DSN contains a plaintext password — pay attention to the access permissions on wherever the config is stored
|
|---|
| Supported clients | Claude Code, Claude Desktop, Cursor | Claude Desktop, Claude Code, VS Code, Cursor, Zed |
|---|
| Tools | 51 | 2 |
|---|