Ext Ops Panel
Open dashboard
Comparison

Sentry (Archived) vs Project Context

Sentry (Archived) is an MCP server published by modelcontextprotocol. Marketplaces we read that list it: 1 (Docker MCP Catalog). Project Context is an MCP server published by sandovalrr. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-13. 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
MarketplaceSentry (Archived)Project Context
Docker MCP Catalog Listed
Version: sha256:f38467297a1e
Forks (GitHub): 11 780
Pulls (Docker Hub): 66 836
Stars (Docker Hub): 7
Stars (GitHub): 91 180
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.4.0
Downloads/month (npm): 220
Downloads/week (npm): 43
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

Sentry (Archived) vs Project Context
FactSentry (Archived)Project Context
Marketplaces that list it11
Stars (GitHub) (differs)91 180 (better)1 (worse)
Pulls (Docker Hub) (differs)66 836No figure on Docker Hub
Forks (GitHub) (differs)11 780 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/sentry)On your machine (@sandovalrr/project-context-mcp)
Transportstdiostdio
Tools it declares (differs)1Not published
Environment variables it asks for (differs)1, secrets among them: 13, secrets among them: 0
Licence (differs)NOASSERTIONNot stated
Repository (differs)github.com/modelcontextprotocol/serversgithub.com/sandovalrr/project-context
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

Sentry (Archived)

In its own words, on Docker MCP Catalog:

A Model Context Protocol server for retrieving and analyzing issues from Sentry.io. This server provides tools to inspect error reports, stacktraces, and other debugging information from your Sentry account.

Project Context

In its own words, on Official MCP Registry:

Safely manage repository-scoped issues across Linear, GitHub Issues, and Jira Cloud.

How to run each

Sentry (Archived) As a local MCP server: Docker image

Claude Code
claude mcp add --env "SENTRY_AUTH_TOKEN=<YOUR_SENTRY_AUTH_TOKEN>" --transport stdio sentry -- docker run -i --rm -e SENTRY_AUTH_TOKEN mcp/sentry

Requires: SENTRY_AUTH_TOKEN (secret)

Project Context As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio project-context -- npx -y @sandovalrr/project-context-mcp

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

Tools each declares

The marketplaces of Project Context publish no list of tools, so we do not compare tools.

Settings each asks for

Only Sentry (Archived) asks for

  • SENTRY_AUTH_TOKEN (secret)

Only Project Context asks for

  • PROJECT_CONTEXT_CONFIG_DIR
  • PROJECT_CONTEXT_CWD
  • PROJECT_CONTEXT_STATE_DIR

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

What it can do: Sentry (Archived) · What it can do: Project Context · 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