Ext Ops Panel
Open dashboard
Comparison

microsoft-events vs Microsoft 365 Calendar

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). Microsoft 365 Calendar is an MCP server published by mindstone. Marketplaces we read that list it: 1 (Official MCP Registry). 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
Marketplacemicrosoft-eventsMicrosoft 365 Calendar
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.2.0
Downloads/month (npm): 354
Downloads/week (npm): 26
Forks (GitHub): 4
Stars (GitHub): 12
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-events vs Microsoft 365 Calendar
Factmicrosoft-eventsMicrosoft 365 Calendar
Marketplaces that list it11
Stars (GitHub) (differs)295 (better)12 (worse)
Forks (GitHub) (differs)85 (better)4 (worse)
Last releaseNot publishedNot published
Where it runs (differs)Remote server (learn.microsoft.com/api/mcp)On your machine (@mindstone/mcp-server-microsoft-calendar)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published5, secrets among them: 0
Parts of the bundle (differs)2Not a bundle
Licence (differs)Apache-2.0Not stated
Repository (differs)github.com/microsoft/build-cligithub.com/mindstone/mcp-servers
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Responded 6 h agono 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

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

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.

Microsoft 365 Calendar

In its own words, on Official MCP Registry:

Microsoft 365 Outlook calendar via Graph: list, get, create, update, respond, free/busy.

How to run each

microsoft-events

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

Microsoft 365 Calendar As a local MCP server: npm package

Claude Code
claude mcp add --env "MS_CLIENT_ID=<YOUR_MS_CLIENT_ID>" --env "MS_CONFIG_DIR=<YOUR_MS_CONFIG_DIR>" --transport stdio mcp-server-microsoft-calendar -- npx -y @mindstone/mcp-server-microsoft-calendar

Requires: MS_CLIENT_ID, MS_CONFIG_DIR

Commands 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

Neither the marketplaces of Microsoft 365 Calendar nor its endpoint list any tools, so we do not compare tools.

Settings each asks for

The marketplaces of microsoft-events publish no settings it asks for, so we do not compare settings.

What it can do: microsoft-events · What it can do: Microsoft 365 Calendar · 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. 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