JFrog Remote MCP Server vs io.github.vish288/mcp-gitlab
JFrog Remote MCP Server is an MCP server published by jfrog. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.vish288/mcp-gitlab is an MCP server published by vish288. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-19. 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 |  JFrog Remote MCP Server |  io.github.vish288/mcp-gitlab |
|---|---|---|
| Official MCP Registry | Listed Version: 0.1.1 Forks (GitHub): 6 Stars (GitHub): 15 Not marked · First seen |
Listed Version: 0.21.0 Downloads/month (PyPI): 19 493 Downloads/week (PyPI): 9 631 Forks (GitHub): 3 Stars (GitHub): 6 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 | JFrog Remote MCP Server | io.github.vish288/mcp-gitlab |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 15 (better) | 6 (worse) |
| Forks (GitHub) (differs) | 6 (better) | 3 (worse) |
| Last release (differs) | Not published | 2026-10-18 |
| Where it runs (differs) | Remote server (myplatform.jfrog.github.io/mcp) | On your machine (mcp-gitlab) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 11, secrets among them: 4 |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/jfrog/jfrog-mcp-server | github.com/vish288/mcp-gitlab |
| Changes in the last 7 days (differs) | 0 | 10 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Not responding since 2026-10-15 | no remote endpoint we check |
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
JFrog Remote MCP Server
MCP Server for JFrog, providing tools for development and artifact management.
io.github.vish288/mcp-gitlab
GitLab MCP server (MCP 2026-07-28): projects, MRs, pipelines, CI/CD, issues; writes or read-only
How to run each
JFrog Remote MCP Server As a remote MCP server
claude mcp add --transport http jfrog-mcp-server https://myplatform.jfrog.github.io/mcpio.github.vish288/mcp-gitlab As a local MCP server: PyPI package
claude mcp add --env "GITLAB_HTTP_BEARER_TOKEN=<YOUR_GITLAB_HTTP_BEARER_TOKEN>" --env "GITLAB_OAUTH_CLIENT_SECRET=<YOUR_GITLAB_OAUTH_CLIENT_SECRET>" --env "GITLAB_OAUTH_JWT_KEY=<YOUR_GITLAB_OAUTH_JWT_KEY>" --env "GITLAB_TOKEN=<YOUR_GITLAB_TOKEN>" --env "GITLAB_URL=<YOUR_GITLAB_URL>" --transport stdio mcp-gitlab -- uvx mcp-gitlabRequires: GITLAB_HTTP_BEARER_TOKEN (secret), GITLAB_OAUTH_CLIENT_SECRET (secret), GITLAB_OAUTH_JWT_KEY (secret), GITLAB_TOKEN (secret), GITLAB_URL
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only JFrog Remote MCP Server has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
The marketplaces of JFrog Remote MCP Server publish no settings it asks for, so we do not compare settings.
What it can do: JFrog Remote MCP Server · What it can do: io.github.vish288/mcp-gitlab · Compare two other plugins
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.