Sentry (Archived) vs Jira Alerts (JSM Operations)
Sentry (Archived) is an MCP server published by modelcontextprotocol. Marketplaces we read that list it: 1 (Docker MCP Catalog). Jira Alerts (JSM Operations) is an MCP server published by rrvrs. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-22. 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) |   Jira Alerts (JSM Operations) |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:f38467297a1e Forks (GitHub): 11 839 Pulls (Docker Hub): 67 095 Stars (Docker Hub): 7 Stars (GitHub): 91 453 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 2.1.0 Downloads/month (npm): 366 Downloads/week (npm): 41 Forks (GitHub): 0 Stars (GitHub): 4 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) | Jira Alerts (JSM Operations) |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 91 453 (better) | 4 (worse) |
| Pulls (Docker Hub) (differs) | 67 095 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 11 839 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/sentry) | On your machine (jira-alerts-mcp) |
| Transport | stdio | stdio |
| Tools it declares (differs) | 1 | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | 4, secrets among them: 2 |
| Licence (differs) | NOASSERTION | Not stated |
| Repository (differs) | github.com/modelcontextprotocol/servers | github.com/rrvrs/jira-alerts-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
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.
Jira Alerts (JSM Operations)
MCP server for Jira Service Management Operations — alerts, on-call schedules and responders
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)
Jira Alerts (JSM Operations) As a local MCP server: npm package
claude mcp add --env "JSM_API_TOKEN=<YOUR_JSM_API_TOKEN>" --env "JSM_CLOUD_ID=<YOUR_JSM_CLOUD_ID>" --env "JSM_OAUTH_TOKEN=<YOUR_JSM_OAUTH_TOKEN>" --transport stdio jira-alerts-mcp -- npx -y jira-alerts-mcpRequires: JSM_API_TOKEN (secret), JSM_CLOUD_ID, JSM_OAUTH_TOKEN (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of Jira Alerts (JSM Operations) 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 Jira Alerts (JSM Operations) asks for
JSM_API_TOKEN (secret)JSM_CLOUD_IDJSM_EMAILJSM_OAUTH_TOKEN (secret)
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: Sentry (Archived) · What it can do: Jira Alerts (JSM Operations) · 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.