Ext Ops Panel
Open dashboard
Comparison

Upload-Post vs Planify

Upload-Post is a plugin bundle for AI coding tools published by mutonby. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). Planify is an MCP server published by planifyapps.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-12. 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
MarketplaceUpload-PostPlanify
Claude Code: claude-plugins-community Listed
Version: 0.2.0
Forks (GitHub): 0
Stars (GitHub): 1
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.4.0
Downloads/month (npm): 403
Downloads/week (npm): 53
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

Upload-Post vs Planify
FactUpload-PostPlanify
Marketplaces that list it11
Stars (GitHub) (differs)1No figure on GitHub
Forks (GitHub) (differs)0No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)Remote server (mcp.upload-post.com/mcp)On your machine (@planifyapps/mcp)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published2, secrets among them: 1
Parts of the bundle (differs)12Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/mutonby/upload-post-plugingithub.com/gsrathoreniks/planifyweb
Changes in the last 7 days00
First seen (differs)2026-10-122026-10-11
Endpoint at the last check (differs)not checked yetno remote endpoint we check

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

Upload-Post

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

Publish to TikTok, Instagram, YouTube, X, LinkedIn, Facebook, Threads, Pinterest, Reddit, Bluesky and Snapchat. Long-form video, short clips, photos, carousels, text, threads, documents and link previews. Schedule cross-platform, repurpose long videos into viral shorts with AI, build Instagram comment-to-DM funnels (AutoDMs), and track analytics. Backed by the Upload-Post MCP server (40+ tools) plus six opinionated skills and three subagents for content strategy, autodm architecture, and upload debugging. Free plan, no credit card required

Planify

In its own words, on Official MCP Registry:

Schedule and publish social posts to Twitter, Instagram, LinkedIn, Pinterest, Bluesky and more.

How to run each

Upload-Post

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

Planify As a local MCP server: npm package

Claude Code
claude mcp add --env "PLANIFY_API_KEY=<YOUR_PLANIFY_API_KEY>" --transport stdio planify -- npx -y @planifyapps/mcp

Requires: PLANIFY_API_KEY (secret)

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

The marketplaces of Upload-Post publish no settings it asks for, so we do not compare settings.

What it can do: Upload-Post · What it can do: Planify · 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