Ext Ops Panel
Open dashboard
Comparison

Hoverfly vs azure-devops-copilot-plugin

Hoverfly is an MCP server published by kapishmalik. Marketplaces we read that list it: 1 (Docker MCP Catalog). 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). 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
MarketplaceHoverflyazure-devops-copilot-plugin
Docker MCP Catalog Listed
Version: sha256:80c9fb90eb15
Forks (GitHub): 3
Stars (GitHub): 9
Not marked · First seen
Not listed
Copilot CLI: github/copilot-plugins Not listed Listed
Version: not stated
Forks (GitHub): 6
Stars (GitHub): 8
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

Hoverfly vs azure-devops-copilot-plugin
FactHoverflyazure-devops-copilot-plugin
Marketplaces that list it11
Stars (GitHub) (differs)9 (better)8 (worse)
Forks (GitHub) (differs)3 (worse)6 (better)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (kapish88/hoverfly-mcp-server)Installs as a plugin bundle
Transport (differs)stdioNot stated
Tools it declares (differs)12Not published
Environment variables it asks forNot publishedNot published
Licence (differs)NOASSERTIONMIT
Repository (differs)github.com/kapishmalik/hoverfly-mcp-servergithub.com/microsoft/azure-devops-copilot-plugin
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

Hoverfly

In its own words, on Docker MCP Catalog:

A Model Context Protocol (MCP) server that exposes Hoverfly as a programmable tool for AI assistants like Cursor, Claude, GitHub Copilot, and others supporting MCP. It enables dynamic mocking of third-party APIs to unblock development, automate testing, and simulate unavailable services during integration.

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.

How to run each

Hoverfly As a local MCP server: Docker image

Claude Code
claude mcp add --transport stdio hoverfly-mcp-server -- docker run -i --rm kapish88/hoverfly-mcp-server

azure-devops-copilot-plugin

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

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

The marketplaces of azure-devops-copilot-plugin publish no list of tools, so we do not compare tools.

Settings each asks for

Neither one's marketplaces publish the settings it asks for.

What it can do: Hoverfly · What it can do: azure-devops-copilot-plugin · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from the public marketplace file https://github.com/github/copilot-plugins/blob/HEAD/.github/plugin/marketplace.json. 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