Ext Ops Panel
Open dashboard
Comparison

gsd-plugin vs Linear-Task-Broker

gsd-plugin is a plugin bundle for AI coding tools published by jnuyens. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). Linear-Task-Broker is an MCP server published by Evozim. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-17. 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
Marketplacegsd-pluginLinear-Task-Broker
Claude Code: claude-plugins-community Listed
Version: 4.5.5
Forks (GitHub): 12
Stars (GitHub): 92
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.0
No figure published
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

gsd-plugin vs Linear-Task-Broker
Factgsd-pluginLinear-Task-Broker
Marketplaces that list it11
Stars (GitHub) (differs)92No figure on GitHub
Forks (GitHub) (differs)12No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server (linear-broker-mcp.vercel.app/api/mcp)
Transport (differs)Not statedSSE
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Hooks it runs (differs)18Not published
Parts of the bundle (differs)126Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/jnuyens/gsd-pluginNot stated
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkAnswered with HTTP 402 (5 days ago)

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

gsd-plugin

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

Get Shit Done Plugin - handles large codebase contexts - structured workflow plugin for Claude Code with 60+ slash commands, 21 agents, MCP server, hooks, and cross-session memory

Linear-Task-Broker

In its own words, on Official MCP Registry:

Integrates agents with Linear software development workflows.

How to run each

gsd-plugin As a Claude Code plugin

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

Linear-Task-Broker As a remote MCP server

Claude Code
claude mcp add --transport sse linear-broker https://linear-broker-mcp.vercel.app/api/mcp --header "payment-signature: <YOUR_PAYMENT_SIGNATURE>"

Requires: payment-signature header

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

Only Linear-Task-Broker has a remote endpoint we check. How we check endpoints

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: gsd-plugin · What it can do: Linear-Task-Broker · 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