Ext Ops Panel
Open dashboard
Comparison

microsoft-foundry vs memo

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). memo is an MCP server published by jagoff. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). As of our marketplace pass on 2026-10-13. 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-foundrymemo
Copilot CLI: github/awesome-copilot Listed
Version: 1.0.14
Forks (GitHub): 261
Stars (GitHub): 2 054
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 4.16.0
Forks (GitHub): 7
Stars (GitHub): 21
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 memo
Factmicrosoft-foundrymemo
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)2 054 (better)21 (worse)
Forks (GitHub) (differs)261 (better)7 (worse)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (mlx-memo)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published10, secrets among them: 0
Hooks it runs (differs)Not published18
Parts of the bundle (differs)Not published7
LicenceMITMIT
Repository (differs)github.com/microsoft/foundry-dev-toolsgithub.com/jagoff/memo
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

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.

memo

In its own words, on Official MCP Registry:

Memory for AI agents — MLX (Apple Silicon) or CPU (Linux), sqlite-vec + BM25, zero cloud.

How to run each

microsoft-foundry

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

memo As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio memo -- uvx mlx-memo

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: memo · 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. 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