Ext Ops Panel
Open dashboard
Comparison

using-cmux vs Hex SSH

using-cmux is a plugin bundle for AI coding tools published by hummer98. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). Hex SSH is an MCP server published by levnikolaevich. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-18. 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
Marketplaceusing-cmuxHex SSH
Claude Code: claude-plugins-community Listed
Version: 1.8.0
Forks (GitHub): 5
Stars (GitHub): 43
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.9.2
Downloads/month (npm): 221
Downloads/week (npm): 71
Forks (GitHub): 88
Stars (GitHub): 578
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

using-cmux vs Hex SSH
Factusing-cmuxHex SSH
Marketplaces that list it11
Stars (GitHub) (differs)43 (worse)578 (better)
Forks (GitHub) (differs)5 (worse)88 (better)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (@levnikolaevich/hex-ssh-mcp)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Hooks it runs (differs)1Not published
Parts of the bundle (differs)4Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/hummer98/using-cmuxgithub.com/levnikolaevich/claude-code-skills
Changes in the last 7 days00
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

using-cmux

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

A Claude Code plugin that teaches the agent to operate cmux, a terminal multiplexer with first-class agent integration. Provides skill patterns and shell wrappers (cmux-send, cmux-read, cmux-send-key, cmux-grid, cfork) for the full sub-agent lifecycle: launch -> trust detection -> prompt -> completion detection -> result collection. Browser automation is covered to the depth needed for a single agent. Companion plugin cmux-team handles multi-agent orchestration on top of using-cmux. macOS / Linux only.

Hex SSH

In its own words, on Official MCP Registry:

Token-efficient SSH MCP with hash-verified files and persistent tmux sessions. 14 tools.

How to run each

using-cmux As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install using-cmux@claude-community

Hex SSH As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio hex-ssh-mcp -- npx -y @levnikolaevich/hex-ssh-mcp

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

Neither one's marketplaces publish the settings it asks for.

What it can do: using-cmux · What it can do: Hex SSH · 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