Ext Ops Panel
Open dashboard
Comparison

Neo4j Cloud Aura Api vs microsoft-365-agents-toolkit

Neo4j Cloud Aura Api is an MCP server published by neo4j-contrib. Marketplaces we read that list it: 1 (Docker MCP Catalog). 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). As of our marketplace pass on 2026-10-12. 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
MarketplaceNeo4j Cloud Aura Apimicrosoft-365-agents-toolkit
Docker MCP Catalog Listed
Version: sha256:c3db64e4e2bc
Forks (GitHub): 262
Pulls (Docker Hub): 16 072
Stars (Docker Hub): 2
Stars (GitHub): 988
Not marked · First seen
Not listed
Copilot CLI: github/copilot-plugins Not listed Listed
Version: 1.1.0
Forks (GitHub): 141
Stars (GitHub): 1 033
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

Neo4j Cloud Aura Api vs microsoft-365-agents-toolkit
FactNeo4j Cloud Aura Apimicrosoft-365-agents-toolkit
Marketplaces that list it11
Stars (GitHub) (differs)988 (worse)1 033 (better)
Pulls (Docker Hub) (differs)16 072No figure on Docker Hub
Forks (GitHub) (differs)262 (better)141 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/neo4j-cloud-aura-api)Installs as a plugin bundle
Transport (differs)stdioNot stated
Tools it declares (differs)12Not published
Environment variables it asks for (differs)8, secrets among them: 1Not published
LicenceMITMIT
Repository (differs)github.com/neo4j-contrib/mcp-neo4jgithub.com/microsoft/work-iq
Changes in the last 7 days00
First seen2026-10-112026-10-11

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

Neo4j Cloud Aura Api

In its own words, on Docker MCP Catalog:

Manage Neo4j Aura database instances through the Neo4j Aura API.

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.

How to run each

Neo4j Cloud Aura Api As a local MCP server: Docker image

Claude Code
claude mcp add --env "NEO4J_AURA_CLIENT_SECRET=<YOUR_NEO4J_AURA_CLIENT_SECRET>" --transport stdio neo4j-cloud-aura-api -- docker run -i --rm -e NEO4J_AURA_CLIENT_SECRET mcp/neo4j-cloud-aura-api

Requires: NEO4J_AURA_CLIENT_SECRET (secret)

microsoft-365-agents-toolkit

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

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

Tools each declares

The marketplaces of microsoft-365-agents-toolkit publish no list of 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: Neo4j Cloud Aura Api · What it can do: microsoft-365-agents-toolkit · Compare two other plugins

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/github/copilot-plugins/blob/HEAD/.github/plugin/marketplace.json. 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