Ext Ops Panel
Open dashboard
Comparison

Slopstop vs io.github.issuecapture/mcp-server

Slopstop is a plugin bundle for AI coding tools published by iansmith. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). io.github.issuecapture/mcp-server is an MCP server published by issuecapture. 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

Where each is published
MarketplaceSlopstopio.github.issuecapture/mcp-server
Claude Code: claude-plugins-community Listed
Version: 4.0.0
Forks (GitHub): 0
Stars (GitHub): 3
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.4
Downloads/month (npm): 126
Downloads/week (npm): 29
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

Slopstop vs io.github.issuecapture/mcp-server
FactSlopstopio.github.issuecapture/mcp-server
Marketplaces that list it11
Stars (GitHub) (differs)3No figure on GitHub
Forks (GitHub) (differs)0No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (@issuecapture/mcp-server)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)22Not a bundle
Licence (differs)CC-BY-SA-4.0Not stated
Repository (differs)github.com/iansmith/ticket-plugingithub.com/issuecapture/issuecapture
Changes in the last 7 days00
First seen (differs)2026-10-122026-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

Slopstop

In its own words, on Claude Code: claude-plugins-community:

A Claude Code plugin that keeps a durable per-ticket plan, findings, and progress log for every ticket you work on — without bloating the ticket itself or polluting the repo. Auto-detects Linear or JIRA as your ticket system at run-time. The four slash commands form a complete loop around a ticket: - /ticket-plugin:start <KEY> fetches the ticket, transitions it to "In Progress", and seeds task_plan.md, findings.md, and progress.md. Resuming an existing ticket reads back the tracking files and prints a summary. - /ticket-plugin:update is a mid-session checkpoint. The ticket stays active. - /ticket-plugin:pause snapshots state and clears the active-ticket pointer. Local-only. - /ticket-plugin:archive pushes the final task plan back to the ticket as its description and posts findings as a comment, then archives the local folder. Refuses to run unless the ticket is already in a terminal state on the ticket system — the user controls the state transition. The aim: fewer wasted tokens re-explaining context between

io.github.issuecapture/mcp-server

In its own words, on Official MCP Registry:

Install the IssueCapture bug reporting widget for Jira. Auto-detects your framework.

How to run each

Slopstop As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install ticket-plugin@claude-community

io.github.issuecapture/mcp-server As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio io-github-issuecapture-mcp-server -- npx -y @issuecapture/mcp-server

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

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

Neither one's marketplaces publish the settings it asks for.

What it can do: Slopstop · What it can do: io.github.issuecapture/mcp-server · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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