Ext Ops Panel
Open dashboard
Comparison

GitHub Chat vs workflow-toolkit

GitHub Chat is an MCP server published by AsyncFuncAI. Marketplaces we read that list it: 1 (Docker MCP Catalog). workflow-toolkit is a plugin bundle for AI coding tools published by dougwithseismic. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). As of our marketplace pass on 2026-10-12. 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 Chatworkflow-toolkit
Docker MCP Catalog Listed
Version: sha256:c9b12a166491
Forks (GitHub): 17
Pulls (Docker Hub): 45 468
Stars (Docker Hub): 4
Stars (GitHub): 90
Not marked · First seen
Not listed
Claude Code: claude-plugins-community Not listed Listed
Version: 1.0.0
Forks (GitHub): 0
Stars (GitHub): 0
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 Chat vs workflow-toolkit
FactGitHub Chatworkflow-toolkit
Marketplaces that list it11
Stars (GitHub) (differs)90 (better)0 (worse)
Pulls (Docker Hub) (differs)45 468No figure on Docker Hub
Forks (GitHub) (differs)17 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/github-chat)Installs as a plugin bundle
Transport (differs)stdioNot stated
Tools it declares (differs)2Not published
Environment variables it asks for (differs)1, secrets among them: 1Not published
Hooks it runs (differs)Not published7
Parts of the bundle (differs)Not a bundle30
Licence (differs)MITApache-2.0
Repository (differs)github.com/asyncfuncai/github-chat-mcpgithub.com/dougwithseismic/workflow-toolkit
Changes in the last 7 days00
First seen (differs)2026-10-112026-10-12

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 Chat

In its own words, on Docker MCP Catalog:

A Model Context Protocol (MCP) for analyzing and querying GitHub repositories using the GitHub Chat API.

workflow-toolkit

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

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 lifecycle hooks. All backed by SQLite, all local.

How to run each

GitHub Chat As a local MCP server: Docker image

Claude Code
claude mcp add --env "GITHUB_API_KEY=<YOUR_GITHUB_API_KEY>" --transport stdio github-chat -- docker run -i --rm -e GITHUB_API_KEY mcp/github-chat

Requires: GITHUB_API_KEY (secret)

workflow-toolkit

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

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

Tools each declares

The marketplaces of workflow-toolkit publish no list of tools, so we do not compare tools.

Settings each asks for

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

What it can do: GitHub Chat · What it can do: workflow-toolkit · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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