Ext Ops Panel
Open dashboard
Comparison

github-issue-worktree vs io.github.HuynhKhanh1402/dejared

github-issue-worktree is a plugin bundle for AI coding tools published by gabrielkoerich. Marketplaces we read that list it: 1 (Community GitHub marketplaces). io.github.HuynhKhanh1402/dejared is an MCP server published by HuynhKhanh1402. Marketplaces we read that list it: 3 (Official MCP Registry, npm registry (MCP servers), 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

Where each is published
Marketplacegithub-issue-worktreeio.github.HuynhKhanh1402/dejared
Community marketplace gabrielkoerich/skills Not seen in the last pass
Version: not stated
Forks (GitHub): 0
Stars (GitHub): 6
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.0
Downloads/month (npm): 568
Downloads/week (npm): 109
Forks (GitHub): 0
Stars (GitHub): 7
Not marked · First seen
npm registry (MCP servers) Not listed Listed
Version: 1.2.1
Downloads/month (npm): 568
Downloads/week (npm): 109
Forks (GitHub): 0
Stars (GitHub): 7
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

github-issue-worktree vs io.github.HuynhKhanh1402/dejared
Factgithub-issue-worktreeio.github.HuynhKhanh1402/dejared
Marketplaces that list it (differs)1 (worse)3 (better)
Stars (GitHub) (differs)6 (worse)7 (better)
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (dejared-mcp)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)Not published2
Licence (differs)Not statedMIT
Repository (differs)github.com/gabrielkoerich/skillsgithub.com/huynhkhanh1402/dejared-mcp
Changes in the last 7 days (differs)30
First seen (differs)2026-10-192026-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

github-issue-worktree

In its own words, on Community GitHub marketplaces:

Manage an isolated worktree per GitHub issue. Register the branch with `gh issue develop`, then create, list, and remove the worktree with `git cow` only, by following the git-worktrees skill. The default directory is `~/.worktrees/<project>/`. Use it when the user explicitly asks to work on a GitHub issue.

io.github.HuynhKhanh1402/dejared

In its own words, on Official MCP Registry:

Explore, analyze, and decompile Java JAR files via MCP

How to run each

github-issue-worktree As a Claude Code plugin

Claude Code
/plugin marketplace add gabrielkoerich/skills
/plugin install github-issue-worktree@skills

io.github.HuynhKhanh1402/dejared As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio dejared -- npx -y dejared-mcp

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: github-issue-worktree · What it can do: io.github.HuynhKhanh1402/dejared · 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. Package data comes from the public npm registry (registry.npmjs.org). 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