han-atlassian vs GitHub
han-atlassian is a plugin bundle for AI coding tools published by testdouble. Marketplaces we read that list it: 1 (Community GitHub marketplaces). GitHub is an MCP server published by github. Marketplaces we read that list it: 2 (Official MCP Registry, Docker MCP Catalog). As of our marketplace pass on 2026-11-09. 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 |  han-atlassian |  GitHub |
|---|---|---|
| Community marketplace testdouble/han | Listed Version: 2.3.1 Forks (GitHub): 28 Stars (GitHub): 342 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 2.1.0 Forks (GitHub): 5 308 Stars (GitHub): 34 320 Not marked · First seen |
| Docker MCP Catalog | Not listed | Listed Version: sha256:f6056fc10bff Forks (GitHub): 5 308 Stars (GitHub): 34 320 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 | han-atlassian | GitHub |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 342 (worse) | 34 320 (better) |
| Forks (GitHub) (differs) | 28 (worse) | 5 308 (better) |
| Last release (differs) | Not published | 2026-11-04 |
| Where it runs (differs) | Installs as a plugin bundle | Remote server or your machine |
| Transport (differs) | Not stated | Streamable HTTP, stdio |
| Tools it declares (differs) | Not published | 40 |
| Environment variables it asks for (differs) | Not published | 1, secrets among them: 1 |
| Parts of the bundle (differs) | 6 | Not a bundle |
| Licence (differs) | Not stated | MIT |
| Repository (differs) | github.com/testdouble/han | github.com/github/github-mcp-server |
| Changes in the last 7 days (differs) | 2 | 5 |
| First seen (differs) | 2026-11-08 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Status out of date: last check 37 h ago returned HTTP 401 |
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
han-atlassian
Atlassian-facing extensions to the Han suite. Adds markdown-to-confluence, which publishes a local Markdown file to a user-specified Confluence page; project-documentation-to-confluence, which runs the han-documentation project-documentation skill and then publishes the result there; investigate-to-confluence, which runs the core investigate skill and publishes the resulting investigation report there; code-overview-to-confluence, which runs the core code-overview skill and publishes the resulting overview there; plan-a-feature-to-confluence, which runs the core plan-a-feature skill and publishes the spec and its companion artifacts there as a page tree; and work-items-to-jira, which creates one Jira ticket per slice from a work-items file. All work through the Atlassian MCP server. Depends on han-core, han-documentation, han-planning, and han-coding (its wrapper skills run skills from each and its wrapped skills dispatch the shared han-core agents), and on han-communication (its wrapped prose-producing skill
GitHub
Connect AI assistants to GitHub - manage repos, issues, PRs, and workflows through natural language.
How to run each
han-atlassian As a Claude Code plugin
/plugin marketplace add testdouble/han
/plugin install han-atlassian@hanGitHub As a remote MCP server
claude mcp add --transport http github-mcp-server https://api.githubcopilot.com/mcp/ --header "Authorization: Bearer <YOUR_TOKEN>"Requires: Authorization header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only GitHub has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of han-atlassian publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of han-atlassian publish no settings it asks for, so we do not compare settings.
What it can do: han-atlassian · What it can do: GitHub · 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. Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.