Ext Ops Panel
Open dashboard
Comparison

agend-sh vs io.github.keshrath/agent-comm

agend-sh is an MCP server published by agend-sh. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.keshrath/agent-comm is an MCP server published by keshrath. Marketplaces we read that list it: 2 (Official MCP Registry, Claude Code: claude-plugins-community). As of our marketplace pass on 2026-10-28. 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
Marketplaceagend-shio.github.keshrath/agent-comm
Official MCP Registry Listed
Version: 1.2.14
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 1.3.12
Downloads/month (npm): 1 015
Downloads/week (npm): 93
Forks (GitHub): 5
Stars (GitHub): 9
Not marked · First seen
Claude Code: claude-plugins-community Not listed Listed
Version: 1.3.9
Forks (GitHub): 5
Stars (GitHub): 9
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

agend-sh vs io.github.keshrath/agent-comm
Factagend-shio.github.keshrath/agent-comm
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)0 (worse)9 (better)
Forks (GitHub) (differs)0 (worse)5 (better)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (ghcr.io/agend-sh/agend-mcp@sha256:4462e2571be0e69003e1be93255e04523342e1e5aa17482ec3d63bd7506bb82f)On your machine (agent-comm)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)1, secrets among them: 1Not published
Parts of the bundle (differs)Not a bundle1
Licence (differs)Not statedMIT
Repository (differs)github.com/agend-sh/cligithub.com/keshrath/agent-comm
Changes in the last 7 days (differs)02
First seen2026-10-112026-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

agend-sh

In its own words, on Official MCP Registry:

Persistent Linux environments for AI agents, with interactive terminals and HTTPS previews.

io.github.keshrath/agent-comm

In its own words, on Official MCP Registry:

Agent intercommunication - messaging, channels, shared state, and real-time events

How to run each

agend-sh As a local MCP server: Docker image

Claude Code
claude mcp add --env "AGEND_API_TOKEN=<YOUR_AGEND_API_TOKEN>" --transport stdio agend-sh -- docker run -i --rm -e AGEND_API_TOKEN --env AGEND_API_TOKEN ghcr.io/agend-sh/agend-mcp@sha256:4462e2571be0e69003e1be93255e04523342e1e5aa17482ec3d63bd7506bb82f

Requires: AGEND_API_TOKEN (secret)

io.github.keshrath/agent-comm As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio agent-comm -- npx -y agent-comm

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 io.github.keshrath/agent-comm publish no settings it asks for, so we do not compare settings.

What it can do: agend-sh · What it can do: io.github.keshrath/agent-comm · 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. Data comes from public marketplace files in GitHub repositories of their authors. 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