Ext Ops Panel
Open dashboard
Comparison

GitHub Chat vs ProjectPulse MCP

GitHub Chat is an MCP server published by AsyncFuncAI. Marketplaces we read that list it: 1 (Docker MCP Catalog). ProjectPulse MCP is an MCP server published by alexbypa. Marketplaces we read that list it: 1 (Official MCP Registry). 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 ChatProjectPulse MCP
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
Official MCP Registry Not listed Listed
Version: 1.8.4
Forks (GitHub): 0
Stars (GitHub): 1
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 ProjectPulse MCP
FactGitHub ChatProjectPulse MCP
Marketplaces that list it11
Stars (GitHub) (differs)90 (better)1 (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)On your machine (projectpulse-mcp)
Transportstdiostdio
Tools it declares (differs)2Not published
Environment variables it asks for1, secrets among them: 11, secrets among them: 1
Licence (differs)MITNot stated
Repository (differs)github.com/asyncfuncai/github-chat-mcpgithub.com/alexbypa/github-projectpulse-mcp
Changes in the last 7 days00
First seen2026-10-112026-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 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.

ProjectPulse MCP

In its own words, on Official MCP Registry:

Monitor GitHub repo health, DORA metrics and CI signals from your AI assistant.

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)

ProjectPulse MCP As a local MCP server: npm package

Claude Code
claude mcp add --env "GITHUB_TOKEN=<YOUR_GITHUB_TOKEN>" --transport stdio github-projectpulse-mcp -- npx -y projectpulse-mcp

Requires: GITHUB_TOKEN (secret)

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

Tools each declares

The marketplaces of ProjectPulse MCP publish no list of tools, so we do not compare tools.

Settings each asks for

Only GitHub Chat asks for

  • GITHUB_API_KEY (secret)

Only ProjectPulse MCP asks for

  • GITHUB_TOKEN (secret)

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: GitHub Chat · What it can do: ProjectPulse MCP · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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