Plur vs Memory Os Cli
A side-by-side look at the Plur and Memory Os Cli MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Plur for knowledge & memory work as a local process; choose Memory Os Cli 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?
Choose Plur when
- You need dedicated capabilities in the Knowledge & Memory domain.
- You prefer a local stdio subprocess transport.
- You want tools like
plur_learn, plur_learn_batch, plur_recall.
Choose Memory Os Cli when
- You need dedicated capabilities in the Knowledge & Memory domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: other.
- You want tools like
get_mcp_identity, remember, recall.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Knowledge & Memory | Knowledge & Memory |
| Quality signal | 59/100 · Good | 65/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | other |
| Pricing | Not declared | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 308 | 12 |
| Directory activity | 3 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | 15 | 20 |
| Full listing | View Plur | View Memory Os Cli |
Tools & capabilities
Plur tools 15
plur_learnStore a correction, preference, or conventionplur_learn_batchStore many engrams in one call (batch dedup + per-item failure isolation)plur_recallRetrieve relevant memories — hybrid (BM25 + embeddings) by default; `mode:"keyword"` for BM25-onlyplur_inject_hybridSelect engrams for current task within token budgetplur_feedbackRate relevance (trains quality over time)plur_forgetRetire a memory (activation decays, eventually pruned)plur_rescopeMove an existing engram to another scope — personal → team, or backplur_session_scopeChange the session's default write scope mid-sessionplur_captureRecord an event — incident, resolution, session milestoneplur_timelineQuery episode history by time, agent, or channelplur_ingestExtract engrams from text automaticallyplur_syncSync via git. `personal` remotes mirror everything (use a private repo); `shared` remotes receive only shared-scope, non-private engrams- +3 more on the listing page
Memory Os Cli tools 20
get_mcp_identityCheck XMemo connection status and the connected account/agent.rememberSave a memory so it can be recalled in future conversations.recallRecall the most relevant saved memories before answering.recall_contextRead a multi-memory context pack. Requires memory:read and does not change content. Use when many memories need explicit budgets; use recall for lightweight answer or get_project_context for project snapshot. max_items/max_tokens bound rendered output.memory_statsShow aggregate statistics for XMemo memories.update_memoryUpdate the content or metadata of an existing memory.explain_memoryExplain why a memory exists or matched a query.restore_memoryRestore a previously deleted memory.add_expenseCreate one XMemo Ledger transaction and backing memory. Requires memory:write; it records a new transaction or reuses a semantic duplicate, and never deletes Ledger records. Use it for a purchase, income, refund, or transfer; use list_ledger_transactions or get_monthly_ledger_summary for reads. amount must be positive; transaction_type defaults to expense; blank transaction_date uses today's UTC date.list_ledger_transactionsShow XMemo Ledger records.get_monthly_ledger_summarySummarize Ledger totals by month and currency.forgetPermanently delete a memory by target.- +8 more on the listing page
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.
Plur
{
"mcpServers": {
"plur": {
"command": "uvx",
"args": [
"plur-hermes"
]
}
}
}
Memory Os Cli
{
"mcpServers": {
"yonro-memory-os-cli": {
"command": "npx",
"args": [
"-y",
"--package",
"@xmemo/client@latest",
"xmemo-mcp"
]
}
}
}
Frequently asked questions
Plur is categorized under Knowledge & Memory and uses a local stdio subprocess. Memory Os Cli belongs to Knowledge & Memory and uses a local stdio subprocess. Pick Plur for knowledge & memory work and Memory Os Cli 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.
Plur has no declared pricing — check the project's own site. Memory Os Cli is listed as free. Auth: other. 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 plur and yonro-memory-os-cli as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Plur has a quality signal of 59/100 (Good) with 3 views, 0 installs and 308 GitHub stars. Memory Os Cli has 65/100 (Great) with 3 views, 0 installs and 12 GitHub stars.