GitHub Chat vs GitLab (Archived)
GitHub Chat is an MCP server published by AsyncFuncAI. Marketplaces we read that list it: 1 (Docker MCP Catalog). GitLab (Archived) is an MCP server published by modelcontextprotocol. Marketplaces we read that list it: 1 (Docker MCP Catalog). 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
| Marketplace | ||
|---|---|---|
| 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 |
Listed Version: sha256:a1b8571a210a Forks (GitHub): 11 780 Pulls (Docker Hub): 81 030 Stars (Docker Hub): 25 Stars (GitHub): 91 180 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 | GitHub Chat | GitLab (Archived) |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 90 (worse) | 91 180 (better) |
| Pulls (Docker Hub) (differs) | 45 468 (worse) | 81 030 (better) |
| Forks (GitHub) (differs) | 17 (worse) | 11 780 (better) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/github-chat) | On your machine (mcp/gitlab) |
| Transport | stdio | stdio |
| Tools it declares (differs) | 2 | 9 |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | 2, secrets among them: 1 |
| Licence (differs) | MIT | NOASSERTION |
| Repository (differs) | github.com/asyncfuncai/github-chat-mcp | github.com/modelcontextprotocol/servers |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-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
A Model Context Protocol (MCP) for analyzing and querying GitHub repositories using the GitHub Chat API.
GitLab (Archived)
MCP Server for the GitLab API, enabling project management, file operations, and more.
How to run each
GitHub Chat As a local MCP server: Docker image
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-chatRequires: GITHUB_API_KEY (secret)
GitLab (Archived) As a local MCP server: Docker image
claude mcp add --env "GITLAB_PERSONAL_ACCESS_TOKEN=<YOUR_GITLAB_PERSONAL_ACCESS_TOKEN>" --transport stdio gitlab -- docker run -i --rm -e GITLAB_PERSONAL_ACCESS_TOKEN mcp/gitlabRequires: GITLAB_PERSONAL_ACCESS_TOKEN (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Only GitHub Chat declares
index_repositoryquery_repository
Only GitLab (Archived) declares
create_branchcreate_issuecreate_merge_requestcreate_or_update_filecreate_repositoryfork_repositoryget_file_contentspush_filessearch_repositories
Both declare
None
Tool names as each marketplace publishes them. More tools is not better in itself: compare what each needs for the job.
Settings each asks for
Only GitHub Chat asks for
GITHUB_API_KEY (secret)
Only GitLab (Archived) asks for
GITLAB_API_URLGITLAB_PERSONAL_ACCESS_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: GitLab (Archived) · Compare two other plugins
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.