Ext Ops Panel
Open dashboard
Comparison

Descope vs Frappe MCP Server

Descope is an MCP server published by descope-sample-apps. Marketplaces we read that list it: 1 (Docker MCP Catalog). Frappe MCP Server is an MCP server published by muthanii. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-24. 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
MarketplaceDescopeFrappe MCP Server
Docker MCP Catalog Listed
Version: sha256:554b2b490c18
Forks (GitHub): 7
Pulls (Docker Hub): 18 212
Stars (Docker Hub): 0
Stars (GitHub): 38
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.2.0
Downloads/month (PyPI): 174
Downloads/week (PyPI): 81
Forks (GitHub): 0
Stars (GitHub): 1
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 Frappe MCP Server
FactDescopeFrappe MCP Server
Marketplaces that list it11
Stars (GitHub) (differs)38 (better)1 (worse)
Pulls (Docker Hub) (differs)18 212No figure on Docker Hub
Forks (GitHub) (differs)7 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/descope)On your machine (frappe-mcp-server)
Transportstdiostdio
Tools it declares (differs)4Not published
Environment variables it asks for (differs)2, secrets among them: 15, secrets among them: 2
Licence (differs)MITNot stated
Repository (differs)github.com/descope-sample-apps/descope-mcp-servergithub.com/muthanii/frappe_mcp
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

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.

Frappe MCP Server

In its own words, on Official MCP Registry:

Interact with Frappe/ERPNext sites — document CRUD, search, and whitelisted method calls

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)

Frappe MCP Server As a local MCP server: PyPI package

Claude Code
claude mcp add --env "FRAPPE_API_KEY=<YOUR_FRAPPE_API_KEY>" --env "FRAPPE_API_SECRET=<YOUR_FRAPPE_API_SECRET>" --env "FRAPPE_URL=<YOUR_FRAPPE_URL>" --transport stdio frappe-mcp -- uvx frappe-mcp-server

Requires: FRAPPE_API_KEY (secret), FRAPPE_API_SECRET (secret), FRAPPE_URL

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

Tools each declares

The marketplaces of Frappe MCP Server 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 Frappe MCP Server asks for

  • FRAPPE_API_KEY (secret)
  • FRAPPE_API_SECRET (secret)
  • FRAPPE_TIMEOUT
  • FRAPPE_URL
  • FRAPPE_VERIFY_SSL

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

What it can do: Descope · What it can do: Frappe MCP Server · 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. 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