Ext Ops Panel
Open dashboard
Comparison

Codebase Memory vs io.github.pi22by7/in-memoria

Codebase Memory is an MCP server published by DeusData. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.pi22by7/in-memoria is an MCP server published by pi22by7. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-18. 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
MarketplaceCodebase Memoryio.github.pi22by7/in-memoria
Official MCP Registry Listed
Version: 0.12.1
Downloads/month (npm): 59 174
Downloads/week (npm): 8 355
Forks (GitHub): 3 850
Stars (GitHub): 46 717
Not marked · First seen
Listed
Version: 0.5.7
Downloads/month (npm): 392
Downloads/week (npm): 66
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

Codebase Memory vs io.github.pi22by7/in-memoria
FactCodebase Memoryio.github.pi22by7/in-memoria
Marketplaces that list it11
Stars (GitHub) (differs)46 717No figure on GitHub
Forks (GitHub) (differs)3 850No figure on GitHub
Last release (differs)2026-10-17Not published
Where it runs (differs)On your machine (codebase-memory-mcp)On your machine (in-memoria)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published1, secrets among them: 1
LicenceNot statedNot stated
Repository (differs)github.com/deusdata/codebase-memory-mcpNot stated
Changes in the last 7 days (differs)20
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

Codebase Memory

In its own words, on Official MCP Registry:

Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.

io.github.pi22by7/in-memoria

In its own words, on Official MCP Registry:

Persistent codebase intelligence that gives AI assistants memory across sessions

How to run each

Codebase Memory As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio codebase-memory-mcp -- npx -y codebase-memory-mcp

io.github.pi22by7/in-memoria As a local MCP server: npm package

Claude Code
claude mcp add --env "OPENAI_API_KEY=<YOUR_OPENAI_API_KEY>" --transport stdio in-memoria -- npx -y in-memoria

Requires: OPENAI_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 Codebase Memory publish no settings it asks for, so we do not compare settings.

What it can do: Codebase Memory · What it can do: io.github.pi22by7/in-memoria · 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