Basic Memory vs SMRITI Memory

A side-by-side look at the Basic Memory and SMRITI Memory MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Basic Memory logoBasic MemoryKnowledge & Memory · Local subprocess (stdio)Persistent, local-first AI memory: a semantic knowledge graph of plain Markdown files that humans and LLMs both read and write. Works with any MCP client, with optional cloud sync and team workspaces.64GoodAuth: no auth requiredSMRITI Memory logoSMRITI MemoryKnowledge & Memory · Local subprocess (stdio)Neuro-inspired long-term memory for AI agents with semantic graph and consolidation.53GoodAuth: not declared

Verdict: choose Basic Memory for knowledge & memory work as a local process; choose SMRITI Memory for knowledge & memory as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Basic Memory logoChoose Basic Memory when

  • You need dedicated capabilities in the Knowledge & Memory domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: No auth required.
  • You want tools like bm_write, bm_read, bm_edit.
Explore Basic Memory

SMRITI Memory logoChoose SMRITI Memory when

  • You need dedicated capabilities in the Knowledge & Memory domain.
  • You prefer a local stdio subprocess transport.
  • You want tools like smriti_encode, smriti_recall, smriti_get_context.
Explore SMRITI Memory

Feature & specification comparison

Rows where the two servers differ are marked.

SpecBasic Memory logoBasic MemorySMRITI Memory logoSMRITI Memory
CategoryKnowledge & MemoryKnowledge & Memory
Quality signal64/100 · Good53/100 · Good
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNo auth requiredNot declared
PricingFreemiumNot declared
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars4,3393
Directory activity 2 views 0 installs 0 upvotes 0 views 0 installs 0 upvotes
Tools1312

Tools & capabilities

Basic Memory tools 13

  • bm_write
  • bm_read
  • bm_edit
  • bm_move
  • bm_delete
  • bm_search
  • bm_list
  • bm_find
  • bm_context
  • bm_man
  • search
  • fetch
  • +1 more on the listing page

SMRITI Memory tools 12

  • smriti_encodeIngests a new memory. Accept `private=True` to exclude from team syncs.
  • smriti_recallRetrieves memories using semantic and graph-based retrieval.
  • smriti_get_contextHelper to inject the current active working memory slots into the context window.
  • smriti_how_well_do_i_knowPerforms a meta-memory confidence check on a given topic.
  • smriti_knowledge_gapsIdentifies topics the agent has identified it needs more information on.
  • smriti_pinMarks a memory as permanent (protects it from strength decay).
  • smriti_forgetSoft-deletes/archives a memory, leaving a cryptographic tombstone.
  • smriti_consolidateTriggers a background System 2 consolidation run.
  • smriti_statsReturns system-wide statistics (total memories, rooms, private counts).
  • smriti_create_private_roomSpawns a private room. All memories inside this room are visibility-isolated.
  • smriti_open_uiLaunches the interactive visual D3.js memory graph in your default browser.
  • smriti_sync_obsidianExports the Semantic Palace graph structures to markdown files in an Obsidian Vault.

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

Basic Memory

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "basicmachines-co-basic-memory": {
      "command": "uvx",
      "args": [
        "--prerelease=allow",
        "basic-memory"
      ]
    }
  }
}

SMRITI Memory

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "smriti-memory": {
      "command": "uvx",
      "args": [
        "smriti-memcore"
      ]
    }
  }
}

Frequently asked questions

Basic Memory is categorized under Knowledge & Memory and uses a local stdio subprocess. SMRITI Memory belongs to Knowledge & Memory and uses a local stdio subprocess. Pick Basic Memory for knowledge & memory work and SMRITI Memory for knowledge & memory.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.

Basic Memory is listed as freemium — a free tier with paid plans. Auth: no auth required. SMRITI Memory has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add basicmachines-co-basic-memory and smriti-memory as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Basic Memory has a quality signal of 64/100 (Good) with 2 views, 0 installs and 4,339 GitHub stars. SMRITI Memory has 53/100 (Good) with 0 views, 0 installs and 3 GitHub stars.