Ext Ops Panel
Open dashboard
Comparison

azure-devops-copilot-plugin vs io.github.getdomovoi/osnova

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). io.github.getdomovoi/osnova is an MCP server published by getdomovoi. 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
Marketplaceazure-devops-copilot-pluginio.github.getdomovoi/osnova
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.12.0
Downloads/month (npm): 2 856
Downloads/week (npm): 68
Forks (GitHub): 0
Stars (GitHub): 1
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 io.github.getdomovoi/osnova
Factazure-devops-copilot-pluginio.github.getdomovoi/osnova
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)8 (better)1 (worse)
Forks (GitHub) (differs)6 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (@getdomovoi/osnova)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published1, secrets among them: 0
Hooks it runs (differs)Not published3
Parts of the bundle (differs)Not published5
Licence (differs)MITApache-2.0
Repository (differs)github.com/microsoft/azure-devops-copilot-plugingithub.com/getdomovoi/osnova
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

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.

io.github.getdomovoi/osnova

In its own words, on Official MCP Registry:

Deterministic code map for AI coding agents: a tree-sitter call graph with exact file:line over MCP.

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.

io.github.getdomovoi/osnova As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio osnova -- npx -y @getdomovoi/osnova 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 azure-devops-copilot-plugin publish no settings it asks for, so we do not compare settings.

What it can do: azure-devops-copilot-plugin · What it can do: io.github.getdomovoi/osnova · 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. 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