GitLab (Archived) vs chat-recall
GitLab (Archived) is an MCP server published by modelcontextprotocol. Marketplaces we read that list it: 1 (Docker MCP Catalog). chat-recall is an MCP server published by munhq. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-13. 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:a1b8571a210a Forks (GitHub): 11 780 Pulls (Docker Hub): 81 183 Stars (Docker Hub): 25 Stars (GitHub): 91 180 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.7.19 Downloads/month (npm): 5 334 Downloads/week (npm): 279 Forks (GitHub): 0 Stars (GitHub): 2 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 | GitLab (Archived) | chat-recall |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 91 180 (better) | 2 (worse) |
| Pulls (Docker Hub) (differs) | 81 183 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 11 780 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/gitlab) | Remote server (chatrecall.dev/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares (differs) | 9 | Not published |
| Environment variables it asks for (differs) | 2, secrets among them: 1 | 4, secrets among them: 0 |
| Licence (differs) | NOASSERTION | Not stated |
| Repository (differs) | github.com/modelcontextprotocol/servers | github.com/munhq/chat-recall |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Answered with HTTP 301 (less than an hour 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
GitLab (Archived)
MCP Server for the GitLab API, enabling project management, file operations, and more.
chat-recall
One searchable history across every AI coding tool, with secret scanning and a shared task board.
How to run each
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/gitlab
Requires: GITLAB_PERSONAL_ACCESS_TOKEN (secret)
chat-recall As a remote MCP server
claude mcp add --transport http chat-recall https://chatrecall.dev/mcp
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only chat-recall has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of chat-recall publish no list of tools, so we do not compare tools.
Settings each asks for
Only GitLab (Archived) asks for
GITLAB_API_URLGITLAB_PERSONAL_ACCESS_TOKEN (secret)
Only chat-recall asks for
CHAT_RECALL_DAEMON_IDLE_SECSCHAT_RECALL_MCP_PROFILECHAT_RECALL_NO_DAEMONCHAT_RECALL_SERVER
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: GitLab (Archived) · What it can do: chat-recall · 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.