Ext Ops Panel
Open dashboard
Comparison

CountLink vs io.github.mcpware/claude-code-organizer

CountLink is an MCP server published by countlink.app. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.mcpware/claude-code-organizer is an MCP server published by mcpware. Marketplaces we read that list it: 2 (Official MCP Registry, Claude Code: claude-plugins-community). 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
MarketplaceCountLinkio.github.mcpware/claude-code-organizer
Official MCP Registry Listed
Version: 1.0.0
No figure published
Not marked · First seen
Listed
Version: 0.10.2
Downloads/month (npm): 346
Downloads/week (npm): 74
Forks (GitHub): 33
Stars (GitHub): 383
Not marked · First seen
Claude Code: claude-plugins-community Not listed Listed
Version: 0.2.5
Forks (GitHub): 33
Stars (GitHub): 383
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

CountLink vs io.github.mcpware/claude-code-organizer
FactCountLinkio.github.mcpware/claude-code-organizer
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)No figure on GitHub383
Forks (GitHub) (differs)No figure on GitHub33
Last releaseNot publishedNot published
Where it runs (differs)Remote server (countlink.app/mcp)On your machine (@mcpware/claude-code-organizer)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)Not a bundle2
Licence (differs)Not statedMIT
Repository (differs)github.com/mrbrunocode/countlinkgithub.com/mcpware/claude-code-organizer
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Responded 15 h agono 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

CountLink

In its own words, on Official MCP Registry:

Shared countdown timers that stay in sync on every screen — no account, any number of viewers.

io.github.mcpware/claude-code-organizer

In its own words, on Official MCP Registry:

Organize Claude Code memories, skills, MCP servers, commands, agents, rules via drag-and-drop.

How to run each

CountLink As a remote MCP server

Claude Code
claude mcp add --transport http countdown https://countlink.app/mcp

io.github.mcpware/claude-code-organizer As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio claude-code-organizer -- npx -y @mcpware/claude-code-organizer

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

Only CountLink 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: CountLink · What it can do: io.github.mcpware/claude-code-organizer · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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