jevmem vs io.github.sumanaddanki/suma-memory
jevmem is a plugin bundle for AI coding tools published by Avinash Jetwani. Marketplaces we read that list it: 1 (Community GitHub marketplaces). io.github.sumanaddanki/suma-memory is an MCP server published by sumanaddanki. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-17. 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 |  io.github.sumanaddanki/suma-memory | |
|---|---|---|
| Community marketplace avinash-jetwani/jevmem | Listed Version: 0.7.3 Forks (GitHub): 10 Stars (GitHub): 127 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.5.0 Downloads/month (npm): 188 Downloads/week (npm): 27 Forks (GitHub): 0 Stars (GitHub): 0 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 | jevmem | io.github.sumanaddanki/suma-memory |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 127 (better) | 0 (worse) |
| Forks (GitHub) (differs) | 10 (better) | 0 (worse) |
| Last release (differs) | 2026-10-16 | Not published |
| Where it runs (differs) | Installs as a plugin bundle | Remote server (sumapro.quadframe.work/mcp) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 2, secrets among them: 1 | 1, secrets among them: 1 |
| Hooks it runs (differs) | 4 | Not published |
| Parts of the bundle (differs) | 5 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/avinash-jetwani/jevmem | github.com/sumanaddanki/suma-mcp |
| Changes in the last 7 days (differs) | 7 | 0 |
| First seen (differs) | 2026-10-13 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Answered with HTTP 404 (8 h ago) |
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
jevmem
Say it once. jevmem saves the decisions, rules and failed approaches from your Claude Code chats to JEVMEM.md in your repo, brings the relevant ones back next session, and checks commands against your saved rules. Needs the jevmem CLI from npm and a TypeSafe API key. Opt-in per project.
io.github.sumanaddanki/suma-memory
Persistent memory for Claude Code and Cursor. Stop re-explaining your project every session.
How to run each
jevmem As a Claude Code plugin
/plugin marketplace add avinash-jetwani/jevmem
/plugin install jevmem@jevmemio.github.sumanaddanki/suma-memory As a remote MCP server
claude mcp add --transport http suma-memory https://sumapro.quadframe.work/mcp --header "Authorization: Bearer <YOUR_TOKEN>"Requires: SUMA_API_KEY (secret), Authorization header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only io.github.sumanaddanki/suma-memory has a remote endpoint we 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
Only jevmem asks for
CLAUDE_PLUGIN_OPTION_TYPESAFE_API_KEY (secret)JEVMEM_PLUGIN_VERSION
Only io.github.sumanaddanki/suma-memory asks for
SUMA_API_KEY (secret)
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: jevmem · What it can do: io.github.sumanaddanki/suma-memory · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. 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.