Sentry (Archived) vs incident-response
Sentry (Archived) is an MCP server published by modelcontextprotocol. Marketplaces we read that list it: 1 (Docker MCP Catalog). incident-response is a plugin bundle for AI coding tools published by Grey Haven Studio. Marketplaces we read that list it: 1 (Community GitHub marketplaces). As of our marketplace pass on 2026-10-21. 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 |   Sentry (Archived) | |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:f38467297a1e Forks (GitHub): 11 830 Pulls (Docker Hub): 67 084 Stars (Docker Hub): 7 Stars (GitHub): 91 419 Not marked · First seen |
Not listed |
| Community marketplace greyhaven-ai/claude-code-config | Not listed | Listed Version: 2.1.0 Forks (GitHub): 5 Stars (GitHub): 30 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 | Sentry (Archived) | incident-response |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 91 419 (better) | 30 (worse) |
| Pulls (Docker Hub) (differs) | 67 084 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 11 830 (better) | 5 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/sentry) | Installs as a plugin bundle |
| Transport (differs) | stdio | Not stated |
| Tools it declares (differs) | 1 | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | Not published |
| Parts of the bundle (differs) | Not a bundle | 5 |
| Licence (differs) | NOASSERTION | MIT |
| Repository (differs) | github.com/modelcontextprotocol/servers | github.com/greyhaven-ai/claude-code-config |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen (differs) | 2026-10-11 | 2026-10-20 |
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)
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.
incident-response
Production incident response system with incident management workflows, intelligent debugging, runbook automation, and postmortem generation. Handles incident detection, triage, mitigation, and learning.
How to run each
Sentry (Archived) As a local MCP server: Docker image
claude mcp add --env "SENTRY_AUTH_TOKEN=<YOUR_SENTRY_AUTH_TOKEN>" --transport stdio sentry -- docker run -i --rm -e SENTRY_AUTH_TOKEN mcp/sentryRequires: SENTRY_AUTH_TOKEN (secret)
incident-response As a Claude Code plugin
/plugin marketplace add greyhaven-ai/claude-code-config
/plugin install incident-response@grey-haven-pluginsCommands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of incident-response publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of incident-response publish no settings it asks for, so we do not compare settings.
What it can do: Sentry (Archived) · What it can do: incident-response · 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.