Ext Ops Panel
Open dashboard
Comparison

@contenthero/mcp vs TokenLab MCP Server

@contenthero/mcp is an MCP server published by @contenthero. Marketplaces we read that list it: 1 (npm registry (MCP servers)). TokenLab MCP Server is an MCP server published by hedging8563. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-10-30. 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
Marketplace@contenthero/mcpTokenLab MCP Server
npm registry (MCP servers) Listed
Version: 0.4.47
Downloads/month (npm): 4 044
Downloads/week (npm): 787
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 0.6.39
Downloads/month (npm): 3 288
Downloads/week (npm): 931
Forks (GitHub): 1
Stars (GitHub): 1
Not marked · First seen
Official MCP Registry Not listed Listed
Version: 0.6.39
Downloads/month (npm): 3 288
Downloads/week (npm): 931
Forks (GitHub): 1
Stars (GitHub): 1
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

@contenthero/mcp vs TokenLab MCP Server
Fact@contenthero/mcpTokenLab MCP Server
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)0 (worse)1 (better)
Forks (GitHub) (differs)0 (worse)1 (better)
Last release (differs)2026-10-29 (better)2026-10-28 (worse)
Where it runs (differs)On your machine (@contenthero/mcp)On your machine (@tokenlabai/mcp-server)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published9, secrets among them: 2
LicenceMITMIT
Repository (differs)github.com/contenthero-ai/contenthero-sdkgithub.com/hedging8563/tokenlab-mcp-server
Changes in the last 7 days (differs)46
First seen (differs)2026-10-122026-10-11

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

@contenthero/mcp

In its own words, on npm registry (MCP servers):

Official ContentHero MCP server. Generate images, video, and audio from any MCP client (Claude Code, Claude Desktop, etc.) using your ContentHero API key.

TokenLab MCP Server

In its own words, on Official MCP Registry:

TokenLab MCP server: generate images and video, call models. 32 default and 89 full-profile tools.

How to run each

@contenthero/mcp

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

TokenLab MCP Server As a local MCP server: npm package

Claude Code
claude mcp add --env "TOKENLAB_API_KEY=<YOUR_TOKENLAB_API_KEY>" --env "TOKENLAB_MANAGEMENT_TOKEN=<YOUR_TOKENLAB_MANAGEMENT_TOKEN>" --transport stdio tokenlab -- npx -y @tokenlabai/mcp-server

Requires: TOKENLAB_API_KEY (secret), TOKENLAB_MANAGEMENT_TOKEN (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 @contenthero/mcp publish no settings it asks for, so we do not compare settings.

What it can do: @contenthero/mcp · What it can do: TokenLab MCP Server · Compare two other plugins

Package data comes from the public npm registry (registry.npmjs.org). 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