New:Introducing Socket Scanning for VS Code Marketplace Extensions.Learn more →
Get Started

@plur-ai/mcp

Package Overview
Dependencies
Maintainers
1
Versions
74
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

@plur-ai/mcp

PLUR MCP server — persistent memory tools for any AI agent

Source
npmnpm
Version
0.13.0
Version published
Weekly downloads
1.7K
-2.32%
Maintainers
1
Weekly downloads
 
Created
Source

@plur-ai/mcp

Give your AI agent persistent memory. One line in your MCP config — corrections, preferences, and conventions persist across sessions. No workflow changes, no cloud, no API costs for search.

Part of PLUR — where, in our tool-routing and local-knowledge benchmark, Haiku with memory outperformed Opus without it at 10x less cost.

Setup (30 seconds)

Claude Code

One command — sets up storage, MCP config, and hooks:

npx @plur-ai/mcp init

Restart Claude Code. Done. Your agent now has persistent memory with automatic injection.

Cursor

Add to .cursor/mcp.json:

{
  "mcpServers": {
    "plur": { "command": "npx", "args": ["-y", "@plur-ai/mcp"] }
  }
}

Windsurf / any MCP client

Same pattern — point it at npx -y @plur-ai/mcp.

That's it. Your agent now has memory. Use your tools as usual — corrections accumulate automatically.

What happens

You correct your agent  →  engram created       →  YAML on your disk
Next session starts     →  relevant ones injected →  agent remembers
You rate the result     →  engram strengthens    →  quality improves

Knowledge is stored as engrams — small assertions that strengthen with use and decay when irrelevant. Search is fully local (BM25 + embeddings), so memory recall costs nothing and works offline. Benchmark methodology →

Tools

Your agent gets these tools automatically:

ToolWhat it does
plur_session_startStart a session — injects relevant engrams for your task
plur_learnStore a memory — correction, preference, convention, or decision
plur_recall_hybridBest default — BM25 + embeddings merged via RRF. Zero cost.
plur_recallKeyword search (BM25 only, instant)
plur_inject_hybridLoad relevant memories for the current task
plur_feedbackRate a memory — trains relevance over time
plur_forgetRetire a memory (history preserved)
plur_session_endEnd a session — captures summary and new learnings
plur_captureRecord a session event
plur_timelineQuery session history
plur_ingestExtract learnings from text
plur_syncSync memory across machines via git
plur_packs_installInstall a shareable memory pack
plur_packs_listList installed packs
plur_statusSystem health

Sync across machines

Your agent can sync memory to any git remote:

Agent: plur_sync({ remote: "git@github.com:you/plur-memory.git" })
→ "Initialized and pushed."

# On another machine, same remote:
Agent: plur_sync()
→ "Synced. Pulled 12 remote commits."

Works with GitHub, GitLab, Gitea, any git host. Your data, your repo.

Configuration

Custom storage path:

{
  "mcpServers": {
    "plur": {
      "command": "npx",
      "args": ["-y", "@plur-ai/mcp"],
      "env": { "PLUR_PATH": "/path/to/storage" }
    }
  }
}

Default: ~/.plur/. Everything is plain YAML — open it, read it, edit it.

Benchmark

MetricScore
LongMemEval overall86.7%
A/B win rate vs no memory89%
House rules accuracy100%

Full methodology →

PackageFor
@plur-ai/coreEngine — use directly in custom agent frameworks
@plur-ai/clawOpenClaw — automatic memory without MCP

License

Apache-2.0 · GitHub · plur.ai

Keywords

ai

FAQs

Package last updated on 09 Jul 2026

Related posts