Ext Ops Panel
Open dashboard
Comparison

microsoft-foundry vs agend-sh

microsoft-foundry is a plugin bundle for AI coding tools published by microsoft. Marketplaces we read that list it: 1 (Copilot CLI: github/awesome-copilot). agend-sh is an MCP server published by agend-sh. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-14. 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
Marketplacemicrosoft-foundryagend-sh
Copilot CLI: github/awesome-copilot Listed
Version: 1.0.14
Forks (GitHub): 262
Stars (GitHub): 2 055
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.2.14
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

microsoft-foundry vs agend-sh
Factmicrosoft-foundryagend-sh
Marketplaces that list it11
Stars (GitHub) (differs)2 055 (better)0 (worse)
Forks (GitHub) (differs)262 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (ghcr.io/agend-sh/agend-mcp@sha256:4462e2571be0e69003e1be93255e04523342e1e5aa17482ec3d63bd7506bb82f)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published1, secrets among them: 1
Licence (differs)MITNot stated
Repository (differs)github.com/microsoft/foundry-dev-toolsgithub.com/agend-sh/cli
Changes in the last 7 days00
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

microsoft-foundry

In its own words, on Copilot CLI: github/awesome-copilot:

Skills and interactive Copilot canvas for designing, configuring, testing and deploying agents to Microsoft Foundry.

agend-sh

In its own words, on Official MCP Registry:

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

How to run each

microsoft-foundry

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

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)

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 microsoft-foundry publish no settings it asks for, so we do not compare settings.

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

Data comes from the public marketplace file https://github.com/github/awesome-copilot/blob/HEAD/.github/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