microsoft-events vs Desktop Commander
microsoft-events is a plugin bundle for AI coding tools published by microsoft. Marketplaces we read that list it: 1 (Copilot CLI: github/awesome-copilot). Desktop Commander is an MCP server published by wonderwhy-er. Marketplaces we read that list it: 6 (Official MCP Registry, Claude Code: claude-plugins-official, Docker MCP Catalog, Claude: knowledge-work-plugins, Claude Code: claude-plugins-community, 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
| Marketplace |  microsoft-events |  Desktop Commander |
|---|---|---|
| Copilot CLI: github/awesome-copilot | Listed Version: 1.0.6 Forks (GitHub): 85 Stars (GitHub): 295 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.3.0 Downloads/month (npm): 926 846 Downloads/week (npm): 204 381 Forks (GitHub): 1 269 Stars (GitHub): 10 027 Not marked · First seen |
| Claude Code: claude-plugins-official | Not listed | Listed Version: 0.2.0 Forks (GitHub): 1 269 Stars (GitHub): 10 027 Not marked · First seen |
| Docker MCP Catalog | Not listed | Listed Version: sha256:5df787069e37 Forks (GitHub): 1 269 Pulls (Docker Hub): 235 429 Stars (Docker Hub): 22 Stars (GitHub): 10 027 Not marked · First seen |
| Claude: knowledge-work-plugins | Not listed | Listed Version: 0.2.0 Forks (GitHub): 1 269 Stars (GitHub): 10 027 Not marked · First seen |
| Claude Code: claude-plugins-community | Not listed | Listed Version: 0.2.0 Forks (GitHub): 1 269 Stars (GitHub): 10 027 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
| Fact | microsoft-events | Desktop Commander |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 6 (better) |
| Stars (GitHub) (differs) | 295 (worse) | 10 027 (better) |
| Pulls (Docker Hub) (differs) | No figure on Docker Hub | 235 429 |
| Forks (GitHub) (differs) | 85 (worse) | 1 269 (better) |
| Last release (differs) | Not published | 2026-10-13 |
| Where it runs (differs) | Remote server (learn.microsoft.com/api/mcp) | On your machine (@wonderwhy-er/desktop-commander) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares (differs) | Not published | 26 |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 2 | 7 |
| Licence (differs) | Apache-2.0 | MIT |
| Repository (differs) | github.com/microsoft/build-cli | github.com/wonderwhy-er/desktopcommandermcp |
| Changes in the last 7 days (differs) | 0 | 3 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 24 h ago | no remote endpoint we check |
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-events
Connect your project to Microsoft Build and Ignite sessions — discover relevant talks, explore what's new for your stack, and plan next steps from your development environment.
Desktop Commander
MCP server for terminal commands, file operations, and process management
How to run each
microsoft-events
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Desktop Commander As a local MCP server: npm package
claude mcp add --transport stdio desktop-commander -- npx -y @wonderwhy-er/desktop-commanderCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only microsoft-events has a remote endpoint we check. How we check endpoints
Tools each declares
Only microsoft-events has
microsoft_code_sample_searchmicrosoft_docs_fetchmicrosoft_docs_search
Only Desktop Commander has
create_directoryedit_blockforce_terminateget_configget_file_infoget_more_search_resultsget_promptsget_recent_tool_callsget_usage_statsgive_feedback_to_desktop_commanderinteract_with_processkill_process
Show the remaining 14
list_directorylist_processeslist_searcheslist_sessionsmove_fileread_fileread_multiple_filesread_process_outputset_config_valuestart_processstart_searchstop_searchwrite_filewrite_pdf
Both have
None
Tool names as the marketplaces declare them and as Ext Ops observed them on the endpoints (microsoft-events as of 2026-10-13). More tools is not better in itself: compare what each needs for the job.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: microsoft-events · What it can do: Desktop Commander · 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 the public marketplace file https://github.com/anthropics/claude-plugins-official/blob/HEAD/.claude-plugin/marketplace.json. 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/anthropics/knowledge-work-plugins/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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.