io.github.zereight/gitlab-mcp
GitLab MCP Server
Is the GitLab MCP server down? It gave no valid answer in the probe of 2026-11-14: not found. One failed probe is not an outage.
GitLab MCP server for projects, merge requests, issues, pipelines, wiki, releases, and more.
not found no valid answer since 2026-11-14 · probed 2026-11-14
npm error 404 Note that you can also install from a npm error 404 tarball, folder, http url, or git url. npm error A complete log of this run can be found in: /
- Run it
- npx -y @zereight/mcp-gitlab@2.3.27 (stdio, probed in a container with the network off)
- Host
- npmjs.com
- Repository
- https://github.com/zereight/gitlab-mcp
- Website
- https://zereight.github.io/gitlab-mcp/
- Registry
- active, updated 2026-11-13 · registry entry
- Changes
- 2 recorded, reachable in 0 of them. A row is added when the result, the tool count or the cost changes.
Compare this server with others.
More servers
Other registry entries on npmjs.com, the ones next to this name; all of them.
- Adobe Commerce MCP io.github.zeluizr/adobe-commerce-mcp · alive
- VTEX IO MCP io.github.zeluizr/vtex-io-mcp · alive
- Zenith io.github.zenitheditor/zenith · crashed on start
- io.github.zerabic/agentweb · alive
- io.github.zero-abd/draw2agent · alive
- io.github.zero520-dot/trencher-agent · alive
- io.github.zeroclaw-labs/zeroclaw-mcp · crashed on start
- io.github.zerodustxyz/zerodust · alive
Servers that mention gitlab.
- com.gitlab/mcp · needs auth
- GitLab MCP Server io.github.jmrplens/gitlab-mcp-server · needs auth
- Gitlab io.github.pipeworx-io/gitlab · alive
- Gitlab Public io.github.pipeworx-io/gitlab-public · alive
- io.github.vaggeliskls/release-notes-mcp · crashed on start
- Remogram io.github.attebury/remogram · alive
- io.github.mrfentmen/appveyor-mcp · alive
- GitLab io.github.vish288/mcp-gitlab · needs args
History
We add a row when the result changes. A server with no change keeps its last row.
| Probed | Result | Init | Tools | Claude | o200k |
|---|---|---|---|---|---|
| 2026-11-14 08:19 | not found | ||||
| 2026-10-17 06:20 | needs env |
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- The package did not start as an MCP server at its probe on 2026-11-14. One failed probe is not an outage: the board calls a package down when it fails again at its next probe, a week later.
- The endpoint answers HTTP 404. The registry entry points to a URL that is not an MCP endpoint any more. Publish a new version of the registry entry with the current URL.