Ext Ops Panel
Open dashboard
Comparison

microsoft-365-agents-toolkit vs Nimbus BCI

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). Nimbus BCI is an MCP server published by nimbusbci. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-16. 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-toolkitNimbus BCI
Copilot CLI: github/copilot-plugins Listed
Version: 1.1.0
Forks (GitHub): 143
Stars (GitHub): 1 033
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.14.2
Downloads/month (PyPI): 1 355
Downloads/week (PyPI): 1 065
Forks (GitHub): 0
Stars (GitHub): 3
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 Nimbus BCI
Factmicrosoft-365-agents-toolkitNimbus BCI
Marketplaces that list it11
Stars (GitHub) (differs)1 033 (better)3 (worse)
Forks (GitHub) (differs)143 (better)0 (worse)
Last release (differs)Not published2026-10-16
Where it runs (differs)Installs as a plugin bundleRemote server (nimbus-mcp.fly.dev/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published5, secrets among them: 2
Licence (differs)MITNot stated
Repository (differs)github.com/microsoft/work-iqgithub.com/nimbusbci/nimbus-mcp
Changes in the last 7 days (differs)05
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 39 h 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.

Nimbus BCI

In its own words, on Official MCP Registry:

AI agents build, train, and analyze BCI/EEG pipelines: data, models, experiments, live sessions.

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.

Nimbus BCI As a remote MCP server

Claude Code
claude mcp add --transport http nimbus-mcp https://nimbus-mcp.fly.dev/mcp

Requires: NIMBUS_MCP_KEY (secret), NIMBUS_TOKEN (secret)

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

Only Nimbus BCI has a remote endpoint we check. How we check endpoints

Tools each declares

Neither the marketplaces of microsoft-365-agents-toolkit nor its endpoint list any tools, so we do not compare tools.

Settings each asks for

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

What it can do: microsoft-365-agents-toolkit · What it can do: Nimbus BCI · 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