Ext Ops Panel
Open dashboard
Comparison

persistent-planning vs Notes

persistent-planning is a plugin bundle for AI coding tools published by TheGlitchKing. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). Notes is an MCP server published by Abhishekkumar2021. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). As of our marketplace pass on 2026-10-14. 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
Marketplacepersistent-planningNotes
Claude Code: claude-plugins-community Listed
Version: 3.0.1
Forks (GitHub): 0
Stars (GitHub): 1
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.4.1
Downloads/month (npm): 870
Downloads/week (npm): 186
Forks (GitHub): 0
Stars (GitHub): 1
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

persistent-planning vs Notes
Factpersistent-planningNotes
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub)11
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (@abhishekmcp/notes)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published3, secrets among them: 0
Hooks it runs (differs)1Not published
Parts of the bundle (differs)101
LicenceMITMIT
Repository (differs)github.com/theglitchking/persistent-planninggithub.com/abhishekkumar2021/mcp-suite
Changes in the last 7 days (differs)02
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

persistent-planning

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

Transforms Claude Code into a Manus-style persistent planner using on-disk markdown files as working memory. Creates structured task directories with task_plan.md and notes.md that persist across sessions. Enables multi-step project tracking, progress visibility, and knowledge storage that survives context resets. Based on proven context engineering principles for long-horizon AI tasks.

Notes

In its own words, on Official MCP Registry:

Local markdown notes: ranked + semantic search, tags, todos, and a wiki-link knowledge graph.

How to run each

persistent-planning As a Claude Code plugin

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

Notes As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio notes -- npx -y @abhishekmcp/notes

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

What it can do: persistent-planning · What it can do: Notes · 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. 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