Ext Ops Panel
Open dashboard
Comparison

pmm vs rutter

pmm is a plugin bundle for AI coding tools published by NominexHQ. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). rutter is an MCP server published by shinytoyrobots. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-22. 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
Marketplacepmmrutter
Claude Code: claude-plugins-community Listed
Version: 2.7.0
Forks (GitHub): 8
Stars (GitHub): 15
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.9.0
Forks (GitHub): 1
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

pmm vs rutter
Factpmmrutter
Marketplaces that list it11
Stars (GitHub) (differs)15 (better)0 (worse)
Forks (GitHub) (differs)8 (better)1 (worse)
Last release (differs)Not published2026-10-21
Where it runs (differs)Installs as a plugin bundleOn your machine (rutter-memory)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published2, secrets among them: 0
Hooks it runs (differs)2Not published
Parts of the bundle (differs)14Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/nominexhq/pmm-plugingithub.com/shinytoyrobots/rutter
Changes in the last 7 days (differs)06
First seen (differs)2026-10-112026-10-16

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

pmm

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

If you have ever had AI hallucinate and make things up (and gaslight you, even): it's because summaries do not preserve nuance. Each /compact cycle summarises and compresses. Decisions lose their rationale. Lessons lose their context. By Monday, you're re-explaining choices you made on Thursday. That's context rot. PMM fixes that. Every session, Claude loads what it already knows, then adds to it. Markdown files, git-backed. No database, no setup. Decisions tracked with rationale: not just what but. git log as your memory audit trail. Memory that compounds, not rots.

rutter

In its own words, on Official MCP Registry:

Recall past decisions and the notes your AI sessions cited, from a local markdown folder.

How to run each

pmm As a Claude Code plugin

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

rutter As a local MCP server: npm package

Claude Code
claude mcp add --env "LIBRARIAN_VAULT_PATH=<YOUR_LIBRARIAN_VAULT_PATH>" --transport stdio rutter -- npx -y rutter-memory

Requires: LIBRARIAN_VAULT_PATH

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

What it can do: pmm · What it can do: rutter · 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. 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