Ext Ops Panel
Open dashboard
Comparison

plansmith vs Agent-Native Plan

plansmith is a plugin bundle for AI coding tools published by gigagookbob. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). Agent-Native Plan is an MCP server published by BuilderIO. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-15. 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
MarketplaceplansmithAgent-Native Plan
Claude Code: claude-plugins-community Listed
Version: 7acbf51
No figure published
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.0
Forks (GitHub): 654
Stars (GitHub): 7 174
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

plansmith vs Agent-Native Plan
FactplansmithAgent-Native Plan
Marketplaces that list it11
Stars (GitHub) (differs)No figure on GitHub7 174
Forks (GitHub) (differs)No figure on GitHub654
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server (plan.agent-native.com/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
LicenceNot statedNot stated
Repository (differs)github.com/gigagookbob/plansmithgithub.com/builderio/agent-native
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checknot checked yet

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

plansmith

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

A planning-focused iterative loop plugin for Claude Code. Progresses through structured phases - explore, draft, critique, revise - with validation at each step. Unlike single-pass planning, it forces fundamentally different work at each stage: the explore phase rejects plan headings, the critique phase rejects finalization attempts. This makes it structurally impossible to skip ahead, producing higher-quality implementation plans before writing any code.

Agent-Native Plan

In its own words, on Official MCP Registry:

Structured visual plans and PR recaps with diagrams, prototypes, annotations, and sharing

How to run each

plansmith As a Claude Code plugin

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

Agent-Native Plan As a remote MCP server

Claude Code
claude mcp add --transport http agent-native-plan https://plan.agent-native.com/mcp

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

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

What it can do: plansmith · What it can do: Agent-Native Plan · 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