Ext Ops Panel
Open dashboard
Comparison

project-artifact vs OpenPlanr Docs

project-artifact is a plugin bundle for AI coding tools published by Anthropic. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-official). OpenPlanr Docs is an MCP server published by openplanr.dev. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-16. 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
Marketplaceproject-artifactOpenPlanr Docs
Claude Code: claude-plugins-official Listed
Version: not stated
Forks (GitHub): 4 295
Stars (GitHub): 38 565
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.0
No figure published
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

project-artifact vs OpenPlanr Docs
Factproject-artifactOpenPlanr Docs
Marketplaces that list it11
Stars (GitHub) (differs)38 565No figure on GitHub
Forks (GitHub) (differs)4 295No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server (openplanr.dev/docs/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)1Not a bundle
LicenceNot statedNot stated
Repository (differs)github.com/anthropics/claude-plugins-officialNot stated
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 3 days ago

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

project-artifact

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

Generate and publish a living project status page — overview & success criteria, the workstream sequence, and next steps — as a shareable claude.ai artifact backed by a per-project config, so refreshes re-gather live state, redeploy the same URL, and report only the delta.

OpenPlanr Docs

In its own words, on Official MCP Registry:

Read-only search and Markdown pages from the OpenPlanr docs, for coding agents.

How to run each

project-artifact As a Claude Code plugin

Claude Code
/plugin install project-artifact@claude-plugins-official

OpenPlanr Docs As a remote MCP server

Claude Code
claude mcp add --transport http docs https://openplanr.dev/docs/mcp

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

Only OpenPlanr Docs has a remote endpoint we check. How we check endpoints

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

Neither one's marketplaces publish the settings it asks for.

What it can do: project-artifact · What it can do: OpenPlanr Docs · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-official/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