Ext Ops Panel
Open dashboard
Comparison

editorial-os vs io.github.shashwatgtm/craft-content-mcp

editorial-os is a plugin bundle for AI coding tools published by EditorialOS. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). io.github.shashwatgtm/craft-content-mcp is an MCP server published by shashwatgtm. 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
Marketplaceeditorial-osio.github.shashwatgtm/craft-content-mcp
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: 2.2.22
Downloads/month (npm): 246
Downloads/week (npm): 25
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

editorial-os vs io.github.shashwatgtm/craft-content-mcp
Facteditorial-osio.github.shashwatgtm/craft-content-mcp
Marketplaces that list it11
Stars (GitHub)00
Forks (GitHub)00
Last release (differs)Not published2026-10-17
Where it runs (differs)Installs as a plugin bundleRemote server (craft-content.gtmhelix.com/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)17Not a bundle
LicenceNot statedNot stated
Repository (differs)github.com/editorialos/editorial-osgithub.com/shashwatgtm/craft-content-mcp
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkNot responding since 2026-10-24

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

editorial-os

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

Content strategy, competitive analysis, editorial calendars, content drafting, email subject lines, and social repurposing — all from one Google Drive folder. Seven commands, five skills, one workflow. Built from 20 years of editorial operations at WIRED, Amazon, Sunset, and the Los Angeles Times.

io.github.shashwatgtm/craft-content-mcp

In its own words, on Official MCP Registry:

CRAFT Content: 8 B2B content tools by Helix GTM Consulting

How to run each

editorial-os As a Claude Code plugin

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

io.github.shashwatgtm/craft-content-mcp As a remote MCP server

Claude Code
claude mcp add --transport http craft-content-mcp https://craft-content.gtmhelix.com/mcp

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

Only io.github.shashwatgtm/craft-content-mcp 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: editorial-os · What it can do: io.github.shashwatgtm/craft-content-mcp · 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