com.leapmemory/memory vs CLS++ Memory
com.leapmemory/memory is an MCP server published by leapmemory.com. Marketplaces we read that list it: 1 (Official MCP Registry). CLS++ Memory is an MCP server published by rajamohan1950. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-15. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  com.leapmemory/memory |  CLS++ Memory |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.0 No figure published Not marked · First seen |
Listed Version: 7.19.0 Downloads/month (PyPI): 95 Downloads/week (PyPI): 24 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | com.leapmemory/memory | CLS++ Memory |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (api.leapmemory.com/mcp) | Remote server (www.clsplusplus.com/mcp) |
| Transport | Streamable HTTP | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 2, secrets among them: 1 |
| Licence | Not stated | Not stated |
| Repository (differs) | Not stated | github.com/rajamohan1950/clsplusplus |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 14 h ago | Not responding since 2026-10-15 |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
com.leapmemory/memory
Long-term memory for AI assistants. Isolated per-user storage, recall across conversations.
CLS++ Memory
Cross-LLM persistent memory: store context once, recall it from any AI model.
How to run each
com.leapmemory/memory As a remote MCP server
claude mcp add --transport http memory https://api.leapmemory.com/mcpCLS++ Memory As a remote MCP server
claude mcp add --transport http cls-memory https://www.clsplusplus.com/mcpRequires: CLS_API_KEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only the endpoint of com.leapmemory/memory responded at the last daily check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
The marketplaces of com.leapmemory/memory publish no settings it asks for, so we do not compare settings.
What it can do: com.leapmemory/memory · What it can do: CLS++ Memory · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.