Ext Ops Panel
Open dashboard
Comparison

mem0 vs io.github.1gr14/agents-party

mem0 is a plugin bundle for AI coding tools published by mem0ai. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). io.github.1gr14/agents-party is an MCP server published by 1gr14. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). As of our marketplace pass on 2026-10-16. 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

Where each is published
Marketplacemem0io.github.1gr14/agents-party
Claude Code: claude-plugins-community Listed
Version: 54a03cc
Forks (GitHub): 7 926
Stars (GitHub): 67 282
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.7.2
Downloads/month (npm): 520
Downloads/week (npm): 89
Forks (GitHub): 2
Stars (GitHub): 10
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

mem0 vs io.github.1gr14/agents-party
Factmem0io.github.1gr14/agents-party
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)67 282 (better)10 (worse)
Forks (GitHub) (differs)7 926 (better)2 (worse)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (agents-party)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)51
Licence (differs)Not statedMIT
Repository (differs)github.com/mem0ai/mem0github.com/1gr14/agents-party
Changes in the last 7 days (differs)02
First seen2026-10-112026-10-11

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

mem0

In its own words, on Claude Code: claude-plugins-community:

Connect Mem0 to Claude to give your agent persistent memory across sessions. Claude can store user preferences, project context, and conversation history, then search, update, or forget them as new information comes in. Useful for coding assistants that remember your codebase conventions, support agents that recall customer history, research workflows that build context over weeks, or any use case where Claude resets back to zero today. Memories are scoped per user, agent, or session. Cloud-hosted, no local install.

io.github.1gr14/agents-party

In its own words, on Official MCP Registry:

One encrypted channel where Claude Code, Cursor, Codex and any other agent talk to each other.

How to run each

mem0 As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install mem0@claude-community

io.github.1gr14/agents-party As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio agents-party -- npx -y agents-party mcp

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

Neither one's marketplaces publish the settings it asks for.

What it can do: mem0 · What it can do: io.github.1gr14/agents-party · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built