Ext Ops Panel
Open dashboard
Comparison

microsoft-docs vs Google Search (via Apify)

microsoft-docs is a plugin bundle for AI coding tools published by MicrosoftDocs. Marketplaces we read that list it: 2 (Claude Code: claude-plugins-official, Copilot CLI: github/awesome-copilot). Google Search (via Apify) is an MCP server published by retracn. 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
Marketplacemicrosoft-docsGoogle Search (via Apify)
Claude Code: claude-plugins-official Listed
Version: 0.3.1
Forks (GitHub): 263
Stars (GitHub): 1 938
Not marked · First seen
Not listed
Copilot CLI: github/awesome-copilot Listed
Version: 0.3.1
Forks (GitHub): 263
Stars (GitHub): 1 938
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.0
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-docs vs Google Search (via Apify)
Factmicrosoft-docsGoogle Search (via Apify)
Marketplaces that list it (differs)2 (better)1 (worse)
Stars (GitHub) (differs)1 938 (better)0 (worse)
Forks (GitHub) (differs)263 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)Remote server (learn.microsoft.com/api/mcp)Remote server (mcp.apify.com)
TransportStreamable HTTPStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)4Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/microsoftdocs/mcpgithub.com/retracn/google-custom-search-api-alternative
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last checknot checked yetnot checked yet

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-docs

In its own words, on Claude Code: claude-plugins-official:

Access official Microsoft documentation, API references, and code samples for Azure, .NET, Windows, and more.

Google Search (via Apify)

In its own words, on Official MCP Registry:

Google web search for AI agents: title, link and snippet in Custom Search JSON API format.

How to run each

microsoft-docs As a Claude Code plugin

Claude Code
/plugin install microsoft-docs@claude-plugins-official

Google Search (via Apify)

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

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: microsoft-docs · What it can do: Google Search (via Apify) · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-official/blob/HEAD/.claude-plugin/marketplace.json. 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