Ext Ops Panel
Open dashboard
Comparison

microsoft-events vs Teamup Calendar MCP by usefulapi

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). Teamup Calendar MCP by usefulapi is an MCP server published by usefulapi.io. 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-eventsTeamup Calendar MCP by usefulapi
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: 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-events vs Teamup Calendar MCP by usefulapi
Factmicrosoft-eventsTeamup Calendar MCP by usefulapi
Marketplaces that list it11
Stars (GitHub) (differs)295 (better)0 (worse)
Forks (GitHub) (differs)85 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)Remote server (learn.microsoft.com/api/mcp)Remote server (teamup-calendar.usefulapi.io/mcp)
TransportStreamable HTTPStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)2Not a bundle
Licence (differs)Apache-2.0Not stated
Repository (differs)github.com/microsoft/build-cligithub.com/m190/usefulapi-mcp
Changes in the last 7 days (differs)02
First seen (differs)2026-10-112026-10-12
Endpoint at the last check (differs)Responded 19 h agoResponded 5 h ago, requires a key

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.

Teamup Calendar MCP by usefulapi

In its own words, on Official MCP Registry:

Read and search Teamup Calendar events and sub-calendars; create, update, delete and undo events.

How to run each

microsoft-events

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

Teamup Calendar MCP by usefulapi As a remote MCP server

Claude Code
claude mcp add --transport http teamup-calendar https://teamup-calendar.usefulapi.io/mcp

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

Both endpoints responded at the last daily check. How we check endpoints

Tools each declares

Neither the marketplaces of Teamup Calendar MCP by usefulapi nor its endpoint list any 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: microsoft-events · What it can do: Teamup Calendar MCP by usefulapi · 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