Ext Ops Panel
Open dashboard
Comparison

gist-design vs PitchDeck Auto

gist-design is a plugin bundle for AI coding tools published by imsaif. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). PitchDeck Auto is an MCP server published by Evozim. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-17. 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
Marketplacegist-designPitchDeck Auto
Claude Code: claude-plugins-community Listed
Version: 1.0.0
Forks (GitHub): 0
Stars (GitHub): 0
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

gist-design vs PitchDeck Auto
Factgist-designPitchDeck Auto
Marketplaces that list it11
Stars (GitHub) (differs)0No figure on GitHub
Forks (GitHub) (differs)0No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server (pitchdeck-auto-mcp.vercel.app/api/mcp)
Transport (differs)Not statedSSE
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)1Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/imsaif/gistNot stated
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkAnswered with HTTP 402 (4 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

gist-design

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

Generates .gist.design files through guided conversation. Asks questions about your product's design decisions, interaction models, positioning, and boundaries, then writes a structured markdown file that AI coding tools (Cursor, Claude Code, Windsurf) and LLMs (ChatGPT, Claude, Perplexity) can read to understand your product accurately instead of guessing. Three modes: /gist-design create (full guided conversation), /gist-design quick (2-3 turn generation), /gist-design audit (scores how AI tools currently describe your product).

PitchDeck Auto

In its own words, on Official MCP Registry:

Interactive sales pitch deck structure generator.

How to run each

gist-design As a Claude Code plugin

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

PitchDeck Auto As a remote MCP server

Claude Code
claude mcp add --transport sse pitchdeck-auto https://pitchdeck-auto-mcp.vercel.app/api/mcp --header "payment-signature: <YOUR_PAYMENT_SIGNATURE>"

Requires: payment-signature header

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

Only PitchDeck Auto 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: gist-design · What it can do: PitchDeck Auto · 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