Ext Ops Panel
Open dashboard
Comparison

Shared team memory for agents vs io.github.yamantaka520/agent-memory-os

Shared team memory for agents is an MCP server published by textforagents.com. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.yamantaka520/agent-memory-os is an MCP server published by yamantaka520. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-25. 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
MarketplaceShared team memory for agentsio.github.yamantaka520/agent-memory-os
Official MCP Registry Listed
Version: 1.0.0
No figure published
Not marked · First seen
Listed
Version: 1.10.1
Downloads/month (PyPI): 1 033
Downloads/week (PyPI): 177
Forks (GitHub): 2
Stars (GitHub): 7
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

Shared team memory for agents vs io.github.yamantaka520/agent-memory-os
FactShared team memory for agentsio.github.yamantaka520/agent-memory-os
Marketplaces that list it11
Stars (GitHub) (differs)No figure on GitHub7
Forks (GitHub) (differs)No figure on GitHub2
Last releaseNot publishedNot published
Where it runs (differs)Remote server (textforagents.com/products/shared-team-agent-memory)On your machine (agent-memory-os)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published2, secrets among them: 0
LicenceNot statedNot stated
Repository (differs)Not statedgithub.com/yamantaka520/agent-memory-os
Changes in the last 7 days (differs)20
First seen (differs)2026-10-192026-10-11
Endpoint at the last check (differs)not checked yetno remote endpoint we check

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

Shared team memory for agents

In its own words, on Official MCP Registry:

Shared project-scoped memory for agent teams: typed records, corroboration, handoff briefs.

io.github.yamantaka520/agent-memory-os

In its own words, on Official MCP Registry:

Local-first memory engine for AI-agent teams: team/project ACL, recall, and federated sync.

How to run each

Shared team memory for agents As a remote MCP server

Claude Code
claude mcp add --transport http shared-team-agent-memory https://textforagents.com/products/shared-team-agent-memory/

io.github.yamantaka520/agent-memory-os As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio agent-memory-os -- uvx agent-memory-os

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

The marketplaces of Shared team memory for agents publish no settings it asks for, so we do not compare settings.

What it can do: Shared team memory for agents · What it can do: io.github.yamantaka520/agent-memory-os · 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.

Where the data comes from: how the catalog is built