All servers / Memory / PLUR MCP server
PLUR MCP server
PLUR MCP server — persistent memory tools for any AI agent
Tested by ConnectATDScore 86 out of 100. Tested 2026-11-19 on package version 0.23.0. Package: @plur-ai/mcp · source
Score breakdown
| Runs | 18 / 20 | |
|---|---|---|
| Tool descriptions | 20 / 20 | |
| Package safety | 20 / 20 | |
| Maintenance | 20 / 20 | |
| Adoption | 8 / 20 |
What we saw
- Starts and answers the MCP handshake: yes (37.9 seconds including download)
- Tools offered: 15
- Last published: 2026-10-30
- Weekly downloads (npm): 759
- License: Apache-2.0 · Direct dependencies: 5
Want this server set up for your team?
ConnectATD builds AI automation and wires up MCP servers like this one. Tell us what you are trying to do.
Talk to ConnectATDTools and how they are described
Agents choose tools from these descriptions. Under each name you can see how many of its parameters are explained.
plur_learn19 of 19 parameters describedCreate an engram — record a reusable learning, preference, or correction. A write is never suppressed by similarity: exact content-hash duplicates NOOP, and anything merely SIMILAR is written and reported back in `dedup.near_duplicates` (closest existing engrams, their cosine scores, and a preview of each neighbour's own statement — read them before moving on; that is what they are for) so you can supersede or merge deliberately. High similarity is a reason to look, not a decision — cosine cannot tell a duplicate from a correction of it. Multi-agent note: in an orchestration that spawns subagents, have the PARENT session own plur_learn writes — spawned subagents should return their findings as text for the parent to persist, rather than each calling plur_learn (tool availability is not guaranteed in every subagent context). See plur-ai/plur#281.
plur_recall9 of 9 parameters describedSearch engrams by topic. Default mode is hybrid (BM25 + local embeddings via RRF) — set mode:"keyword" for BM25-only. Local search plus, when a configured enterprise store is part of the current project/work — or when the scope (or the default scope this session registered itself) is a personal user: scope and a remote store is configured with that same scope (exact match, case-insensitive; that rule adds only the matching store, though a store set to dial: always or a trusted project remote can still add others) — one live timeout-bounded recall per remote host merged in (a `remote_stores` block + warning appears when a host is degraded; no host configured or implicated = fully local). Note: a project-scope filter also returns personal-family engrams (local, global, user:*, agent:*); an explicit scope=global recall returns ALL personal-family engrams — wider than scope=global INJECT, which is targeted to the global namespace only.
plur_feedback4 of 4 parameters describedRate an engram's usefulness — trains injection relevance over time. Supports single or batch mode.
plur_forget4 of 4 parameters describedRetire an engram by ID or search term — marks it as no longer active without deleting history
plur_packs_uninstall1 of 1 parameter describedUninstall an engram pack by name — removes the pack and all its engrams
plur_validate_meta5 of 5 parameters describedTest a meta-engram template against engrams from a new domain — updates confidence and domain_coverage. A meta-engram that fails validation in a third domain is demoted (top → mop) or, below top level, RETIRED.
plur_status3 of 3 parameters describedReturn system health — running version, engram count, episode count, pack count, storage root. Optionally filter engram counts by domain prefix and/or creation date.
plur_receipt1 of 1 parameter describedCounted report of what your memory retrieved for you: engrams stored, how many were retrieved and how often, which are most relied on, and how much of the store is dormant. Local and read-only; every figure is directly counted, never estimated. IMPORTANT when relaying to the user: `activation_rate` is COVERAGE over the logging window (≈ how much of the store was surfaced), NOT a quality or effectiveness score — it is naturally low and FALLS as more engrams are added, so never present it as "memory is N% effective". A `summary` line is included; prefer relaying that. NOT plur_provenance: this counts usage across the whole store; plur_provenance says where a single memory came from.
plur_doctor2 of 2 parameters describedDiagnose the PLUR ENGINE (embedder, hybrid search, remote-store auth) — not hook/MCP wiring. Reports whether the embedding model loaded, whether hybrid search is fully operational, and — for any configured enterprise/remote store — whether its auth is valid (probes /api/v1/me and decodes token expiry), so a dead or soon-to-expire token surfaces instead of hiding behind a "healthy" report. Run this first when recall feels off or team engrams stop syncing. Does NOT check .cursor/mcp.json, .cursor/hooks.json, or the live MCP tool count — for that, run the `plur doctor` CLI command in a terminal (a different, more thorough check with the same name).
plur_session_start3 of 3 parameters describedStart a session — inject relevant engrams for your task. Call at the beginning of every session.
plur_session_end3 of 3 parameters describedEnd a session. BEFORE calling this tool, review the conversation and extract learnings: 1. Corrections the user made ("no, use X not Y") → type: behavioral 2. Preferences stated ("always X", "never Y") → type: behavioral 3. Codebase patterns discovered (naming, structure, conventions) → type: architectural 4. Technical facts learned (API quirks, config, gotchas) → type: procedural 5. Terminology defined or clarified → type: terminological Include at least one engram_suggestion if ANYTHING was learned. An empty suggestions array means nothing worth remembering happened — this should be rare.
plur_tensions15 of 15 parameters describedTension lifecycle (#181). Default: list persisted tension records (unresolved first). scan:true runs an LLM contradiction scan, persists NEW detections as records, and skips already-recorded pairs. Lifecycle actions: action:"confirm" (real conflict), action:"dismiss" (false positive — pair suppressed from future scans), action:"resolve" + winner:<engram_id> (loser engram retired). Scan requires OPENAI_API_KEY or OPENROUTER_API_KEY env var, or explicit llm_base_url + llm_api_key args.
plur_tensions_purgeno parametersPurge all conflict relations from local engrams — removes accumulated false positives from the legacy tension-detection system
plur_report_failure5 of 5 parameters describedReport a failure for a procedural engram — triggers procedure evolution via LLM if configured. Only works on procedural engrams. Max 3 revisions per procedure per 24h.
plur_admin2 of 2 parameters describedGateway to the 30 PLUR operations that are not top-level tools under the current profile (collapsed into one dispatch tool so Cursor's ~40-tool-per-workspace limit is not exhausted by PLUR alone). A plur_* name missing from tools/list means it moved HERE — not that the MCP is unavailable. Calling convention: { action: "<tool name>", args: { ...that tool's normal arguments } } — same arguments, same validation, same result as a direct call. Example: { action: "plur_recall_hybrid", args: { query: "deploy checklist" } }. Send { action: "help" } for every action's one-line description and argument schema. Actions, grouped — inject: plur_inject, plur_inject_hybrid · packs: plur_packs_discover, plur_packs_export, plur_packs_install, plur_packs_list, plur_packs_preview · stores: plur_stores_add, plur_stores_list · sync: plur_sync, plur_sync_status · other: plur_capture, plur_episode_to_engram, plur_extract_meta, plur_history, plur_ingest, plur_learn_batch, plur_meta_engrams, plur_outbox, plur_pin, plur_profile, plur_promote, plur_provenance, plur_recall_hybrid, plur_rescope, plur_scopes_discover, plur_session_scope, plur_similarity_search, plur_suggest_scope, plur_timeline.
Tested in a sandbox with an empty environment: no API keys, a throwaway folder, nothing from a real account. A passing test shows the server runs and responds. It is not a security audit.