Ext Ops Panel
Open dashboard
Comparison

microsoft-365-agents-toolkit vs mcp.tc directory

microsoft-365-agents-toolkit is a plugin bundle for AI coding tools published by microsoft. Marketplaces we read that list it: 1 (Copilot CLI: github/copilot-plugins). mcp.tc directory is an MCP server published by mcp.tc. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-17. 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-365-agents-toolkitmcp.tc directory
Copilot CLI: github/copilot-plugins Listed
Version: 1.1.0
Forks (GitHub): 145
Stars (GitHub): 1 033
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.1.0
No figure published
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-365-agents-toolkit vs mcp.tc directory
Factmicrosoft-365-agents-toolkitmcp.tc directory
Marketplaces that list it11
Stars (GitHub) (differs)1 033No figure on GitHub
Forks (GitHub) (differs)145No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server (mcp.tc/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Licence (differs)MITNot stated
Repository (differs)github.com/microsoft/work-iqNot stated
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 2 days ago

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-365-agents-toolkit

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

Toolkit for building Microsoft 365 Copilot declarative agents — scaffolding, JSON manifest development, and capability configuration.

mcp.tc directory

In its own words, on Official MCP Registry:

Search the mcp.tc directory of MCP servers: URLs, install commands, sign-in types, tools, setup.

How to run each

microsoft-365-agents-toolkit

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

mcp.tc directory As a remote MCP server

Claude Code
claude mcp add --transport http mcp-tc https://mcp.tc/mcp

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

Only mcp.tc directory has a remote endpoint we check. How we check endpoints

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-365-agents-toolkit · What it can do: mcp.tc directory · 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. 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