Descope vs Django Admin MCP
Descope is an MCP server published by descope-sample-apps. Marketplaces we read that list it: 1 (Docker MCP Catalog). Django Admin MCP is an MCP server published by 7tg. Marketplaces we read that list it: 1 (Official MCP Registry). 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
| Marketplace |  Descope |  Django Admin MCP |
|---|---|---|
| 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 |
| Official MCP Registry | Not listed | Listed Version: 0.10.1 Downloads/month (PyPI): 2 001 Downloads/week (PyPI): 432 Forks (GitHub): 5 Stars (GitHub): 28 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
| Fact | Descope | Django Admin MCP |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 38 (better) | 28 (worse) |
| Pulls (Docker Hub) (differs) | 17 877 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 7 (better) | 5 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/descope) | On your machine (django-admin-mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares (differs) | 4 | Not published |
| Environment variables it asks for (differs) | 2, secrets among them: 1 | 1, secrets among them: 0 |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/descope-sample-apps/descope-mcp-server | github.com/7tg/django-admin-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-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
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.
Django Admin MCP
Django admin models over MCP: CRUD, actions, history, autocomplete — capped by Django permissions.
How to run each
Descope As a local MCP server: Docker image
claude mcp add --env "DESCOPE_MANAGEMENT_KEY=<YOUR_DESCOPE_MANAGEMENT_KEY>" --transport stdio descope -- docker run -i --rm -e DESCOPE_MANAGEMENT_KEY mcp/descopeRequires: DESCOPE_MANAGEMENT_KEY (secret)
Django Admin MCP
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Requires: host
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of Django Admin 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 Django Admin MCP asks for
host
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: Descope · What it can do: Django Admin 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. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.