Ext Ops Panel
Open dashboard
Comparison

agend-sh vs fleet

agend-sh is an MCP server published by agend-sh. Marketplaces we read that list it: 1 (Official MCP Registry). fleet is an MCP server published by lion-zhang. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-29. 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-shfleet
Official MCP Registry Listed
Version: 1.2.14
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 0.6.1
Downloads/month (PyPI): 0
Downloads/week (PyPI): 236
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

agend-sh vs fleet
Factagend-shfleet
Marketplaces that list it11
Stars (GitHub)00
Forks (GitHub)00
Last release (differs)Not published2026-10-25
Where it runs (differs)On your machine (ghcr.io/agend-sh/agend-mcp@sha256:4462e2571be0e69003e1be93255e04523342e1e5aa17482ec3d63bd7506bb82f)On your machine (agents-fleet)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)1, secrets among them: 1Not published
Licence (differs)Not statedMIT
Repository (differs)github.com/agend-sh/cligithub.com/lion-zhang/fleet
Changes in the last 7 days (differs)05
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.

fleet

In its own words, on Official MCP Registry:

Every machine you have, for your agent: free GPUs, jobs, served models, software, over SSH.

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)

fleet As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio fleet -- uvx agents-fleet 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

The marketplaces of fleet publish no settings it asks for, so we do not compare settings.

What it can do: agend-sh · What it can do: fleet · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. 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