Ext Ops Panel
Open dashboard
Comparison

io.github.TinySuiteHQ/tinycontext vs repo-memory-mcp

io.github.TinySuiteHQ/tinycontext is an MCP server published by TinySuiteHQ. Marketplaces we read that list it: 1 (Official MCP Registry). repo-memory-mcp is an MCP server published by Umarjaum. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-28. 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
Marketplaceio.github.TinySuiteHQ/tinycontextrepo-memory-mcp
Official MCP Registry Listed
Version: 0.5.1
Forks (GitHub): 3
Stars (GitHub): 9
Not marked · First seen
Listed
Version: 0.2.0
Downloads/month (PyPI): 353
Downloads/week (PyPI): 62
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

io.github.TinySuiteHQ/tinycontext vs repo-memory-mcp
Factio.github.TinySuiteHQ/tinycontextrepo-memory-mcp
Marketplaces that list it11
Stars (GitHub) (differs)9 (better)0 (worse)
Forks (GitHub) (differs)3 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (docker.io/marcellm01/tinycontext:v0.5.1)On your machine (repo-memory-mcp-ai)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)8, secrets among them: 1Not published
LicenceNot statedNot stated
Repository (differs)github.com/tinysuitehq/tinycontextgithub.com/umarjaum/repo-memory-mcp
Changes in the last 7 days00
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

io.github.TinySuiteHQ/tinycontext

In its own words, on Official MCP Registry:

Token-light local memory with SQLite hybrid retrieval for MCP agents.

repo-memory-mcp

In its own words, on Official MCP Registry:

Persistent local memory for MCP-compatible AI coding agents, stored per repository in SQLite.

How to run each

io.github.TinySuiteHQ/tinycontext As a local MCP server: Docker image

Claude Code
claude mcp add --env "OTEL_EXPORTER_OTLP_HEADERS=<YOUR_OTEL_EXPORTER_OTLP_HEADERS>" --transport stdio tinycontext -- docker run -i --rm -e OTEL_EXPORTER_OTLP_HEADERS docker.io/marcellm01/tinycontext:v0.5.1

Requires: OTEL_EXPORTER_OTLP_HEADERS (secret)

repo-memory-mcp As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio repo-memory-mcp -- uvx repo-memory-mcp-ai

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

What it can do: io.github.TinySuiteHQ/tinycontext · What it can do: repo-memory-mcp · 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