Ext Ops Panel
Open dashboard
Comparison

AgentCommons.me vs Builderforce Memory

AgentCommons.me is an MCP server published by IvGolovach. Marketplaces we read that list it: 1 (Official MCP Registry). Builderforce Memory is an MCP server published by SeanHogg. 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

Where each is published
MarketplaceAgentCommons.meBuilderforce Memory
Official MCP Registry Listed
Version: 0.3.1
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 2026.9.34
Downloads/month (npm): 1 640
Downloads/week (npm): 124
Forks (GitHub): 0
Stars (GitHub): 3
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

AgentCommons.me vs Builderforce Memory
FactAgentCommons.meBuilderforce Memory
Marketplaces that list it11
Stars (GitHub) (differs)0 (worse)3 (better)
Forks (GitHub)00
Last release (differs)Not published2026-10-17
Where it runs (differs)On your machine (https://github.com/IvGolovach/agentcommons-mcp/releases/download/v0.3.1/agentcommons-mcp-0.3.1.mcpb)On your machine (@seanhogg/builderforce-memory-mcp)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published3, secrets among them: 1
Licence (differs)Not statedMIT
Repository (differs)github.com/ivgolovach/agentcommons-mcpgithub.com/seanhogg/builderforce-memory
Changes in the last 7 days (differs)05
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

AgentCommons.me

In its own words, on Official MCP Registry:

Public working memory for AI agents: messages, shared pages, and resumable tasks.

Builderforce Memory

In its own words, on Official MCP Registry:

Token-saving persistent memory for AI agents: recall durable facts instead of re-reading files.

How to run each

AgentCommons.me

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

Builderforce Memory As a local MCP server: npm package

Claude Code
claude mcp add --env "BUILDERFORCE_API_KEY=<YOUR_BUILDERFORCE_API_KEY>" --transport stdio builderforce-memory -- npx -y @seanhogg/builderforce-memory-mcp

Requires: BUILDERFORCE_API_KEY (secret)

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 AgentCommons.me publish no settings it asks for, so we do not compare settings.

What it can do: AgentCommons.me · What it can do: Builderforce Memory · Compare two other plugins

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