Log inSubmit server
Shodh Memory logo

Shodh Memory

by varun29ankuS

Offline MCP memory and task management with semantic recall, knowledge graphs, reminders, and local backups.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Shodh Memory

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "varun29ankus-shodh-memory": {
      "command": "npx",
      "args": [
        "-y",
        "@shodh/memory-mcp"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Automated check passed— started and listed 38 tools correctly (1mo ago).

Overview

varun29ankuS/shodh-memory MCP server gives AI agents persistent local memory, semantic retrieval, reminders, and GTD-style task tracking. It stores and searches information without an LLM or external database, using local embeddings, graph relationships, memory decay, and usage-based strengthening. Reach for it when an agent needs context across sessions, offline operation, or a combined memory-and-todo workspace. Local use does not require an API key.

Use cases

  • Remember project decisions across agent sessions
  • Recall user preferences and prior context
  • Track todos, projects, reminders, and recurring work
  • Back up and restore an agent's local memory
  • Repair and verify the semantic memory index

Key features

  • Local semantic and graph-based memory recall
  • Hebbian strengthening and activation decay
  • Persistent reminders and GTD-style todos
  • Memory backup, verification, purge, and restore
  • Vector-index diagnostics and repair
  • Offline operation without an LLM API

Tools38

What Shodh Memory lets your agent do. Expand a tool for its parameters.

Verified live~5.3k tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

19/20 checks healthy over the last 78d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 7d ago via OSV.dev · @shodh/memory-mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars316Stargazers on the source repository.
npm downloads424Package downloads in the last 30 days.
Last commit1d agoMost recent push to the default branch.
Availability100%Our rolling endpoint + install checks that succeeded.
Install checkPassedOur sandbox started it and listed its tools.
Tools exposed38Callable tools this server registers over MCP.
Directory activity6 viewsConfig copies, upvotes, and views on AllMCPs.

How Shodh Memory works

What varun29ankuS/shodh-memory MCP server does

varun29ankuS/shodh-memory MCP server adds persistent memory and task management to MCP clients. Agents can save decisions, preferences, project details, and other context with remember, then retrieve it through semantic, associative, temporal, hybrid, spatial, mission, or action-outcome recall modes. Tag searches, recent-context summaries, memory statistics, and memory listing support inspection and targeted retrieval.

The server also exposes reminders and a GTD-oriented todo system. Agents can create projects and tasks, assign priorities, contexts, due dates, and subtasks, then search, reorder, complete, update, archive, or delete them. Recurring todos create their next occurrence when completed.

How it works

Storage and retrieval run locally rather than sending content to an LLM or a hosted database. The system uses on-device MiniLM embeddings through ONNX Runtime for semantic search. It can extract entities with a local GLiNER model, fall back to rules, and build typed graph relationships from text. Graph traversal supports related-memory retrieval and causal tracing.

Memory is organized into working, session, and long-term tiers. Frequently used memories receive stronger activation, while unused information decays. Recalling one item can activate related items, and repeated connection use can preserve those relationships. Content-hash deduplication prevents identical memories from being stored twice.

The proactive_context tool is intended to run first for every user message. It accepts the message as context, retrieves relevant prior information, and automatically ingests the context for future sessions. Token tools report session usage and can reset the counter after a new or compressed conversation.

Setup and configuration

For an MCP client, install the published npm wrapper with:

Terminal
npx -y @shodh/memory-mcp

A Claude Desktop or Cursor configuration can run that command with -y and @shodh/memory-mcp as its arguments. Local operation needs no API key; the local setup generates one automatically. Remote deployments can pass a SHODH_API_KEY value to authenticate access.

The project also documents a unified shodh CLI, Python installation, Rust usage, and Docker deployment. The standalone server can listen on port 3030 in the documented Docker example, with a mounted volume used for data persistence. The MCP wrapper is the relevant installation path when an MCP client launches the server locally.

Tools and capabilities

The available capabilities include:

  • Store, recall, tag-search, summarize, list, inspect, and delete memories.
  • Check vector-index health and re-index orphaned memories.
  • Create, list, verify, purge, and restore local backups.
  • Review consolidation reports covering strengthening, decay, graph edges, extraction, and maintenance.
  • Track token usage and reset a token session.
  • Set, list, and dismiss time- or context-triggered reminders.
  • Manage todos and projects, including priorities, due dates, subtasks, ordering, completion, and archiving.

Limitations and notes

varun29ankuS/shodh-memory MCP server is designed for local, offline use, but the first run may download the configured local AI model. Its memory intelligence is algorithmic and does not use an LLM in the storage or recall path. Remote deployments require the API-key configuration described in the README, while local clients do not.

Restoring a backup replaces the current user's data, and the documentation recommends restarting the server afterward. The verify_index and repair_index tools are available for diagnosing and repairing memories that exist in storage but are missing from the searchable vector index. The project describes edge-device and robotics support, including Zenoh and ROS2 readiness, but those deployment paths are separate from the basic MCP client setup.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Shodh Memory

Run `npx -y @shodh/memory-mcp` in an MCP client configuration.

Yes. The README provides an MCP configuration for Claude Desktop and also lists Cursor support.

No API key is needed for local use. Remote servers can use `SHODH_API_KEY`.

Yes. The `recall` tool searches memories and todos using semantic similarity and returns matching results from both.

Related MCP servers

All in Knowledge & Memory All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewShodh Memory AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/varun29ankus-shodh-memory?style=directory)](https://allmcps.com/mcp/varun29ankus-shodh-memory)
HTML Embed
<a href="https://allmcps.com/mcp/varun29ankus-shodh-memory"><img src="https://allmcps.com/api/badge/varun29ankus-shodh-memory?style=directory" alt="Shodh Memory on AllMCPs" /></a>