Ext Ops Panel
Open dashboard
Comparison

Descope vs Microsoft Graph MCP

Descope is an MCP server published by descope-sample-apps. Marketplaces we read that list it: 1 (Docker MCP Catalog). Microsoft Graph MCP is an MCP server published by Servosity. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). As of our marketplace pass on 2026-10-15. 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
MarketplaceDescopeMicrosoft Graph MCP
Docker MCP Catalog Listed
Version: sha256:554b2b490c18
Forks (GitHub): 7
Pulls (Docker Hub): 17 874
Stars (Docker Hub): 0
Stars (GitHub): 38
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.2.3
Forks (GitHub): 12
Stars (GitHub): 59
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

Descope vs Microsoft Graph MCP
FactDescopeMicrosoft Graph MCP
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)38 (worse)59 (better)
Pulls (Docker Hub) (differs)17 874No figure on Docker Hub
Forks (GitHub) (differs)7 (worse)12 (better)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/descope)On your machine (https://github.com/Servosity/msp-skills/releases/download/microsoft-graph-v0.2.3/microsoft-graph-mcp.mcpb)
Transportstdiostdio
Tools it declares (differs)4Not published
Environment variables it asks for2, secrets among them: 12, secrets among them: 1
Licence (differs)MITApache-2.0
Repository (differs)github.com/descope-sample-apps/descope-mcp-servergithub.com/servosity/msp-skills
Changes in the last 7 days (differs)02
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

Descope

In its own words, on Docker MCP Catalog:

The Descope Model Context Protocol (MCP) server provides an interface to interact with Descope's Management APIs, enabling the search and retrieval of project-related information.

Microsoft Graph MCP

In its own words, on Official MCP Registry:

The maintained single-binary successor to the retiring mgc - every MSP-relevant Microsoft Graph

How to run each

Descope As a local MCP server: Docker image

Claude Code
claude mcp add --env "DESCOPE_MANAGEMENT_KEY=<YOUR_DESCOPE_MANAGEMENT_KEY>" --transport stdio descope -- docker run -i --rm -e DESCOPE_MANAGEMENT_KEY mcp/descope

Requires: DESCOPE_MANAGEMENT_KEY (secret)

Microsoft Graph MCP As a Claude Code plugin

Claude Code
/plugin marketplace add servosity/msp-skills
/plugin install microsoft-graph@msp-skills

Requires: MICROSOFT_GRAPH_TOKEN (secret)

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 Graph MCP publish no list of tools, so we do not compare tools.

Settings each asks for

Only Descope asks for

  • DESCOPE_MANAGEMENT_KEY (secret)
  • DESCOPE_PROJECT_ID

Only Microsoft Graph MCP asks for

  • MICROSOFT_GRAPH_BASE_URL
  • MICROSOFT_GRAPH_TOKEN (secret)

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: Descope · What it can do: Microsoft Graph MCP · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from public marketplace files in GitHub repositories of their authors. 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