Ext Ops Panel
Open dashboard
Comparison

Marketing vs Post Assembly

Marketing is a plugin bundle for AI coding tools published by Anthropic. Marketplaces we read that list it: 1 (Claude: knowledge-work-plugins). Post Assembly is an MCP server published by postassembly.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-13. 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
MarketplaceMarketingPost Assembly
Claude: knowledge-work-plugins Listed
Version: 1.2.0
Forks (GitHub): 3 345
Stars (GitHub): 29 497
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.1
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

Marketing vs Post Assembly
FactMarketingPost Assembly
Marketplaces that list it11
Stars (GitHub) (differs)29 497No figure on GitHub
Forks (GitHub) (differs)3 345No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server (app.postassembly.com/api/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)21Not a bundle
LicenceNot statedNot stated
Repository (differs)github.com/anthropics/knowledge-work-pluginsgithub.com/toddwilkens/postassembly-app
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 7 h ago, requires a key

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

Marketing

In its own words, on Claude: knowledge-work-plugins:

Create content, plan campaigns, and analyze performance across marketing channels. Maintain brand voice consistency, track competitors, and report on what's working.

Post Assembly

In its own words, on Official MCP Registry:

Editorial tools for LinkedIn. Capture ideas, draft posts, build narrative arcs, manage a schedule.

How to run each

Marketing As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/knowledge-work-plugins
/plugin install marketing@knowledge-work-plugins

Post Assembly As a remote MCP server

Claude Code
claude mcp add --transport http post-assembly https://app.postassembly.com/api/mcp --header "x-api-key: <YOUR_X_API_KEY>"

Requires: x-api-key header

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

Only Post Assembly 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: Marketing · What it can do: Post Assembly · Compare two other plugins

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