Ext Ops Panel
Open dashboard
Comparison

azure-devops-copilot-plugin vs MCP Memory Graph

azure-devops-copilot-plugin is a plugin bundle for AI coding tools published by microsoft. Marketplaces we read that list it: 1 (Copilot CLI: github/copilot-plugins). MCP Memory Graph is an MCP server published by RetroRobAI. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-12. 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
Marketplaceazure-devops-copilot-pluginMCP Memory Graph
Copilot CLI: github/copilot-plugins Listed
Version: not stated
Forks (GitHub): 6
Stars (GitHub): 8
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.1.1
No figure published
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

azure-devops-copilot-plugin vs MCP Memory Graph
Factazure-devops-copilot-pluginMCP Memory Graph
Marketplaces that list it11
Stars (GitHub) (differs)8No figure on GitHub
Forks (GitHub) (differs)6No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (mcp-memory-graph)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Licence (differs)MITNot stated
Repository (differs)github.com/microsoft/azure-devops-copilot-plugingithub.com/retrorobai/mcp-memory-graph
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

azure-devops-copilot-plugin

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

Bring Azure DevOps work-item, repository, and pull-request workflows into GitHub Copilot.

MCP Memory Graph

In its own words, on Official MCP Registry:

Authority-weighted memory graph for AI agents with conflict detection and semantic search.

How to run each

azure-devops-copilot-plugin

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

MCP Memory Graph As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio mcp-memory-graph -- uvx mcp-memory-graph

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: azure-devops-copilot-plugin · What it can do: MCP Memory Graph · Compare two other plugins

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