Comparison

file-ticket vs GitHub Issue MCP

file-ticket is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑16.

file-ticket is a plugin bundle for AI coding tools published by iowarp. No marketplace we read lists it any more. GitHub Issue MCP is an MCP server published by sarim-aliii. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-20. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.

Where each is published

Where each is published
Marketplace	file-ticket	GitHub Issue MCP
Community marketplace iowarp/clio-kit	Removed on 2026-10-16 Version: 0.3.0 Forks (GitHub): 5 Stars (GitHub): 8 Not marked · First seen 2026-10-13	Not listed
Official MCP Registry	Not listed	Listed Version: 1.1.2 Downloads/month (npm): 194 Downloads/week (npm): 25 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen 2026-10-11

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

file-ticket vs GitHub Issue MCP
Fact	file-ticketno longer listed · 2026-10-16	GitHub Issue MCP
Marketplaces that list it (differs)	0	1
Stars (GitHub) (differs)	8	0
Forks (GitHub) (differs)	5	0
Last release	Not published	Not published
Where it runs (differs)	Installs as a plugin bundle	On your machine (github-issue-mcp)
Transport (differs)	Not stated	stdio
Tools it declares	Not published	Not published
Environment variables it asks for (differs)	Not published	4, secrets among them: 2
Licence (differs)	Apache-2.0	Not stated
Repository (differs)	github.com/iowarp/clio-coder	github.com/sarim-aliii/github-issue-mcp
Changes in the last 7 days (differs)	2	0
First seen (differs)	2026-10-13	2026-10-11

Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.

What to use instead of file-ticket

Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.

backlog-swipe-triage

Quickly swipe through backlog issues to triage decisions like assign, needs-info, defer, close, or ignore.

by James Montemagno · Plugin bundle

Listed on: Copilot CLI: github/awesome-copilot · Describes a similar job
Slopstop

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…

by iansmith · Plugin bundle

Listed on: Claude Code: claude-plugins-community · Describes a similar job
simple-workflow

Complete development lifecycle plugin with built-in ticket management, Generator-Evaluator quality pipeline, and context conservation for long-running sessions.

by aimsise · Plugin bundle

Listed on: Claude Code: claude-plugins-community · Describes a similar job
workflow-toolkit

Get up to speed in any codebase, any size. Non-opinionated workflow plugin with session journaling, local task tracking, GitHub issue sync, knowledge base generation, and…

by dougwithseismic · Plugin bundle

Listed on: Claude Code: claude-plugins-community · Describes a similar job
sentry-triage

Scan live Sentry issues in a Copilot canvas, group them by urgency, and hand issues off for tracking or a fix PR.

by Liz Tom · Plugin bundle

Listed on: Copilot CLI: github/awesome-copilot · Describes a similar job
Atlassian Teamwork Graph CLI

Teamwork Graph CLI is Atlassian's agent-first interface to your entire work context: Jira issues, Confluence pages, Bitbucket PRs, along with your connected third-party data…

by atlassian-labs · Plugin bundle

Listed on: Claude Code: claude-plugins-official, Copilot CLI: github/awesome-copilot · Describes a similar job

Its card, with similar plugins by marketplace

What each says it does

file-ticket

In its own words, on Community GitHub marketplaces:

Turns something noticed mid-session into a tracker issue: captures evidence, dedups against existing issues, composes a labeled issue with acceptance criteria, confirms, and creates it via gh. Not for batch ticket creation from a PRD; use backlog. Not for diagnosing an existing issue; use fix-issue.

GitHub Issue MCP

In its own words, on Official MCP Registry:

AI-powered MCP server for generating GitHub issues and detecting semantic duplicates.

How to run each

file-ticket

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

GitHub Issue MCP As a local MCP server: npm package

Claude Code

claude mcp add --env "GEMINI_API_KEY=<YOUR_GEMINI_API_KEY>" --env "GITHUB_OWNER=<YOUR_GITHUB_OWNER>" --env "GITHUB_REPO=<YOUR_GITHUB_REPO>" --env "GITHUB_TOKEN=<YOUR_GITHUB_TOKEN>" --transport stdio github-issue-mcp -- npx -y github-issue-mcp

Requires: GEMINI_API_KEY (secret), GITHUB_OWNER, GITHUB_REPO, GITHUB_TOKEN (secret)

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

The marketplaces of file-ticket publish no settings it asks for, so we do not compare settings.

What it can do: file-ticket · What it can do: GitHub Issue MCP · Compare two other plugins

Data comes from public marketplace files in GitHub repositories of their authors. 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 2026-10-20. We publish no contact details for plugin publishers.