Ext Ops Panel
Open dashboard
Comparison

Dart AI vs persistent-planning

Dart AI is an MCP server published by its-dart. Marketplaces we read that list it: 1 (Docker MCP Catalog). 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). As of our marketplace pass on 2026-10-13. 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
MarketplaceDart AIpersistent-planning
Docker MCP Catalog Listed
Version: sha256:fe45ca6be893
Forks (GitHub): 27
Pulls (Docker Hub): 17 063
Stars (Docker Hub): 3
Stars (GitHub): 128
Not marked · First seen
Not listed
Claude Code: claude-plugins-community Not listed Listed
Version: 3.0.1
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

Dart AI vs persistent-planning
FactDart AIpersistent-planning
Marketplaces that list it11
Stars (GitHub) (differs)128 (better)1 (worse)
Pulls (Docker Hub) (differs)17 063No figure on Docker Hub
Forks (GitHub) (differs)27 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/dart)Installs as a plugin bundle
Transport (differs)stdioNot stated
Tools it declares (differs)16Not published
Environment variables it asks for (differs)2, secrets among them: 1Not published
Hooks it runs (differs)Not published1
Parts of the bundle (differs)Not a bundle10
LicenceMITMIT
Repository (differs)github.com/its-dart/dart-mcp-servergithub.com/theglitchking/persistent-planning
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

Dart AI

In its own words, on Docker MCP Catalog:

Dart AI Model Context Protocol (MCP) server.

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.

How to run each

Dart AI As a local MCP server: Docker image

Claude Code
claude mcp add --env "DART_TOKEN=<YOUR_DART_TOKEN>" --transport stdio dart -- docker run -i --rm -e DART_TOKEN mcp/dart

Requires: DART_TOKEN (secret)

persistent-planning As a Claude Code plugin

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

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

The marketplaces of persistent-planning publish no list of tools, so we do not compare tools.

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: Dart AI · What it can do: persistent-planning · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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