Ext Ops Panel
Open dashboard
Comparison

outputai vs Practonaut

outputai is a plugin bundle for AI coding tools published by growthxai. Marketplaces we read that list it: 3 (Claude Code: claude-plugins-official, Claude Code: claude-plugins-community, Community GitHub marketplaces). Practonaut is an MCP server published by godarg. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-26. 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
MarketplaceoutputaiPractonaut
Claude Code: claude-plugins-official Listed
Version: 0.3.0
Forks (GitHub): 15
Stars (GitHub): 445
Not marked · First seen
Not listed
Claude Code: claude-plugins-community Listed
Version: 0.3.0
Forks (GitHub): 15
Stars (GitHub): 445
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.2.0
Downloads/month (npm): 240
Downloads/week (npm): 240
Forks (GitHub): 0
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

outputai vs Practonaut
FactoutputaiPractonaut
Marketplaces that list it (differs)3 (better)1 (worse)
Stars (GitHub) (differs)445 (better)0 (worse)
Forks (GitHub) (differs)15 (better)0 (worse)
Last release (differs)2026-10-16 (worse)2026-10-16 (better)
Where it runs (differs)Installs as a plugin bundleOn your machine (practonaut)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Hooks it runs (differs)1Not published
Parts of the bundle (differs)57Not a bundle
LicenceNot statedNot stated
Repository (differs)github.com/growthxai/outputgithub.com/godarg/practonaut
Changes in the last 7 days00
First seen (differs)2026-10-112026-10-14

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

outputai

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

Output.ai workflow development toolkit for Claude Code. Adds 5 specialist agents (planner, builder, debugger, prompt writer, quality reviewer), 40+ slash-command skills covering scaffolding, debugging, evaluation, and credential management, plus a SessionStart hook that auto-loads Output SDK conventions so Claude understands the framework before the first prompt.

Practonaut

In its own words, on Official MCP Registry:

Local practice gym for AI agents on real apps: practice Excalidraw tasks, get a reproducible score.

How to run each

outputai As a Claude Code plugin

Claude Code
/plugin install outputai@claude-plugins-official

Practonaut As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio practonaut -- npx -y practonaut mcp --task excalidraw/connect

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: outputai · What it can do: Practonaut · 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 public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Data comes from public marketplace files in GitHub repositories of their authors. 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