← Back to directory
S

Shodh-Memory MCP Server

Official
A local, LLM-free cognitive memory MCP server.
Category
Database #20 of 58
Stars
★ 306 Very popular
Transport
stdio (local process)
Runtime
Node.js · Prebuilt binary
Credentials
No credential needed
License
Apache-2.0
Last commit
Tools
51
59FMRS · C

The supplied materials describe an Apache-2.0 licensed, version 0.2.0 MCP server using stdio transport for local cognitive memory. Its main capabilities are LLM-free semantic search and knowledge graphs, together with memory, session, todo, project, reminder, statistics, and backup management.

Strongest · Documentation 14/20 Weakest · Reliability 9/20

Reliability
9/20
Security and permissions
11/20
Maintenance
12/20
Documentation
14/20
Setup experience
13/20
Why each score
Reliability 9/20
The manifest declares an npm stdio package, version, and default local backend, while the README describes the MCP tools and API paths, so a normal startup path is plausible. However, this is a static review with no actual initialization handshake, tool-list response, committed tests, or key-path coverage evidence. Backend auto-download, IPC/HTTP fallback, and whether all 51 tools match real behavior are unverifiable, so points are deducted and the score remains at or below the static-review ceiling of 12.
Security and permissions 11/20
The default API URL is 127.0.0.1, the API key is marked secret, API endpoints are documented as requiring X-API-Key, and local binding, CORS, IPC, and production settings are described. These show basic boundary awareness. Points are deducted because user_id is explicitly not an authorization tenant, the remote Zenoh example listens on 0.0.0.0, and destructive, purge, restore, and reset tools have no documented confirmation, privilege separation, or misuse safeguards. Disclosure of external network access, automatic model downloads, and complete data flows is also incomplete. No evidence establishes a red-line violation.
Maintenance 12/20
The repository is not archived and provides an Apache-2.0 license, a named GitHub owner, version 0.2.0, and publication paths for npm, crates.io, and PyPI; the README also shows a CI badge. Points are deducted because the supplied material contains no commit history, actual CI workflow, dependency-update policy, vulnerability-response channel, or maintenance commitment. The open-issue count cannot establish response quality, so this indicates some maintenance signals but not sustained governance.
Documentation 14/20
The README covers installation, client configuration, authentication variables, platforms, deployment modes, tool categories, API examples, performance claims, and diagnostic commands. Its coverage is broad. Points are deducted because per-tool parameters and return schemas, error semantics, retention and privacy limits, backup/restore risks, and reviewable test evidence are missing. The claims of no API keys also need clearer qualification given remote authentication and automatic key generation.
Setup experience 13/20
The README provides short Claude Code and JSON client configurations using npx -y @shodh/memory-mcp, and lists Linux, macOS, Windows, Docker, and Python paths. Points are deducted because the MCP client still depends on an automatically downloaded or separately running backend, IPC versus HTTP selection is relatively complex, and remote deployment requires additional authentication and proxy configuration. No committed end-to-end installation or connection verification evidence is supplied, so the score stays below the static-review ceiling of 15.

Static review · not runListed 2026-08-14

Read the FMRS scoring method →

Fit and risk

What it can accessUses the networkConnects to a database

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.

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.

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.

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.

Setup

Before you start

Runtime:Node.js · Prebuilt binary

SHODH_API_KEY optionalsecret API key for backend authentication; auto-generated locally, only needed for remote servers.
SHODH_API_KEYS optionalsecret Comma-separated API keys for production deployments; generated by the admin.
Other optional settings (19)
SHODH_API_URL optional URL of the shodh-memory backend, default http://127.0.0.1:3030; not needed for local runs.
SHODH_USER_ID optional Logical memory namespace, default "default"; not an authorization tenant.
SHODH_ENV optional Set to production to enable production mode.
SHODH_HOST optional Server bind address, default 127.0.0.1.
SHODH_PORT optional Server port, default 3030.
SHODH_MEMORY_PATH optional Data directory, e.g. /var/lib/shodh.
SHODH_IPC_ENABLED optional Local IPC is enabled by default; set to false to disable.
SHODH_IPC_ENDPOINT optional Optional platform-specific IPC socket path override.
SHODH_IPC_REQUIRED optional Set to true to fail closed instead of falling back to HTTP.
SHODH_REQUEST_TIMEOUT optional Request timeout in seconds, default 60.
SHODH_MAX_CONCURRENT optional Max concurrent requests, default 200.
SHODH_ROCKSDB_BLOCK_CACHE_MB optional Shared RocksDB block cache in MiB, default 256.
SHODH_CORS_ORIGINS optional Allowed CORS origins, e.g. https://app.example.com.
SHODH_ZENOH_ENABLED optional Set to true to enable Zenoh transport for robotics.
SHODH_ZENOH_MODE optional Zenoh mode: peer, client, or router.
SHODH_ZENOH_LISTEN optional Zenoh listen endpoints, e.g. tcp/0.0.0.0:7447.
SHODH_ZENOH_CONNECT optional Zenoh connect endpoints, e.g. tcp/1.2.3.4:7447.
SHODH_ZENOH_PREFIX optional Key expression prefix, default shodh.
SHODH_ZENOH_AUTO_TOPICS optional JSON array configuring auto-subscribed ROS2 topics via zenoh-bridge-ros2dds.

Ensure the local Shodh-Memory backend is running at the default address, http://127.0.0.1:3030, then add the server with: claude mcp add shodh-memory -- npx -y @shodh/memory-mcp. Claude Desktop or Cursor can use the supplied MCP configuration. For a remote backend, set SHODH_API_URL and, when required, SHODH_API_KEY; SHODH_USER_ID defaults to default.

.mcp.json
{"mcpServers":{"shodh-memory":{"command":"npx","args":["-y","@shodh/memory-mcp"]}}}

Shown for Claude Code. Other clients may use a different file or key (VS Code uses "servers") — the configurator below converts it.

.vscode/mcp.json
{
  "servers": {
    "shodh-memory": {
      "command": "npx",
      "args": [
        "-y",
        "@shodh/memory-mcp"
      ]
    }
  }
}

Goes in your project's .vscode/mcp.json (VS Code uses a "servers" key).

Terminal
claude mcp add shodh-memory -- npx -y @shodh/memory-mcp

Run it in a terminal; replace any <…> placeholders with your own values first.

Check that it works

After running claude mcp add shodh-memory -- npx -y @shodh/memory-mcp, the shodh-memory tools such as remember and recall should appear in your client's tool list. Ask the assistant to remember a preference, then ask for it back — a correct answer confirms the connection.

Troubleshooting

  1. Confirm that the Shodh-Memory backend is running at http://127.0.0.1:3030.
  2. Check that SHODH_API_URL points to the correct backend.
  3. For remote backends, verify that SHODH_API_KEY is set and valid.
  4. Confirm that npx is available and that npx -y @shodh/memory-mcp starts successfully.
  5. Use shodh status or shodh doctor to check backend health.
  6. If indexing is abnormal, inspect verify_index, repair_index, and memory_health.

Things to try

Once connected, you can ask your AI assistant things like:

  • Remember that I prefer dark mode — this is a decision
  • Recall what you've stored about my user preferences
  • List all of my current todos
  • Show me the summary of this session

Tools 51

remember writes
Stores a memory.
recall read-only
Searches memories semantically.
recall_by_tags read-only
Searches memories by tags.
proactive_context read-only
Retrieves proactive memory context relevant to the current context.
context_summary read-only
Creates a summary of memory context.
list_memories read-only
Lists memories.
read_memory read-only
Reads a specified memory.
forget destructive
Deletes or forgets a specified memory.
Show 43 more tools
quick_recall read-only
Quickly retrieves memories.
query read-only
Queries memories and related knowledge.
topic read-only
Retrieves memories for a topic.
what_i_know read-only
Queries information known by the system.
recent_memories read-only
Lists recent memories.
pending_work read-only
Queries pending work.
count read-only
Counts memories.
memory_health read-only
Checks memory-system health.
session_summary read-only
Retrieves a session summary.
session_digest read-only
Creates a session digest.
session_history read-only
Queries session history.
fact_narratives read-only
Retrieves fact narratives.
purge_facts destructive
Purges fact records.
add_todo writes
Adds a todo item.
list_todos read-only
Lists todo items.
update_todo writes
Updates a todo item.
complete_todo writes
Completes a todo item.
delete_todo destructive
Deletes a todo item.
reorder_todo writes
Reorders todo items.
list_subtasks read-only
Lists subtasks.
add_todo_comment writes
Adds a comment to a todo item.
list_todo_comments read-only
Lists todo comments.
update_todo_comment writes
Updates a todo comment.
delete_todo_comment destructive
Deletes a todo comment.
todo_stats read-only
Retrieves todo statistics.
add_project writes
Adds a project.
list_projects read-only
Lists projects.
archive_project writes
Archives a project.
delete_project destructive
Deletes a project.
set_reminder writes
Sets a reminder.
list_reminders read-only
Lists reminders.
dismiss_reminder writes
Dismisses a reminder.
memory_stats read-only
Retrieves memory-system statistics.
verify_index read-only
Verifies the index.
repair_index writes
Repairs the index.
token_status read-only
Checks token status.
reset_token_session writes
Resets the token session.
consolidation_report read-only
Retrieves a memory-consolidation report.
backup_create writes
Creates a backup.
backup_list read-only
Lists backups.
backup_verify read-only
Verifies a backup.
backup_restore writes
Restores a backup.
backup_purge destructive
Purges backups.

Use cases

Persisting cross-session memory for Claude Code, Claude Desktop, or Cursor.
Running local semantic search, tag search, and knowledge-graph queries.
Managing an agent's todos, projects, reminders, and session summaries.
Storing mission, sensor, and action-outcome memories for robots and edge devices.

Supported clients

Claude Code
Claude Desktop
Cursor

Listed from the project's documentation, not tested by this site.

Overview

Shodh-Memory provides persistent cognitive memory for AI agents and robots. It performs semantic search, Hebbian learning, memory decay, knowledge-graph construction, causal tracing, and related-memory activation with local algorithms, without cloud services, external databases, or LLM calls during storage and recall. The server uses stdio MCP transport and connects to a backend that defaults to http://127.0.0.1:3030.

Similar servers

Source revision 902daf8394e7 Data synced 2026-10-11 Read the FMRS scoring method