Ext Ops Panel
Open dashboard
Comparison

Descope vs claude-permissions-plugin

Descope is an MCP server published by descope-sample-apps. Marketplaces we read that list it: 1 (Docker MCP Catalog). claude-permissions-plugin is a plugin bundle for AI coding tools published by broven. Marketplaces we read that list it: 1 (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
MarketplaceDescopeclaude-permissions-plugin
Docker MCP Catalog Listed
Version: sha256:554b2b490c18
Forks (GitHub): 7
Pulls (Docker Hub): 17 877
Stars (Docker Hub): 0
Stars (GitHub): 38
Not marked · First seen
Not listed
Community marketplace broven/claude-permissions-plugin Not listed Listed
Version: 0.3.3
Forks (GitHub): 1
Stars (GitHub): 5
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 claude-permissions-plugin
FactDescopeclaude-permissions-plugin
Marketplaces that list it11
Stars (GitHub) (differs)38 (better)5 (worse)
Pulls (Docker Hub) (differs)17 877No figure on Docker Hub
Forks (GitHub) (differs)7 (better)1 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/descope)Installs as a plugin bundle
Transport (differs)stdioNot stated
Tools it declares (differs)4Not published
Environment variables it asks for (differs)2, secrets among them: 1Not published
Hooks it runs (differs)Not published1
Parts of the bundle (differs)Not a bundle2
LicenceMITMIT
Repository (differs)github.com/descope-sample-apps/descope-mcp-servergithub.com/broven/claude-permissions-plugin
Changes in the last 7 days (differs)02
First seen (differs)2026-10-112026-10-15

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.

claude-permissions-plugin

In its own words, on Community GitHub marketplaces:

Bash permission management for Claude Code: auto-approve compound commands, sync project permissions to global settings, and analyze permission logs to discover missing allow rules.

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)

claude-permissions-plugin As a Claude Code plugin

Claude Code
/plugin marketplace add broven/claude-permissions-plugin
/plugin install claude-permissions-plugin@broven-claude-permissions-plugin

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

Tools each declares

The marketplaces of claude-permissions-plugin publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of claude-permissions-plugin publish no settings it asks for, so we do not compare settings.

What it can do: Descope · What it can do: claude-permissions-plugin · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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