io.github.nunolima/gitlab-docs-mcp
GitLab Documentation MCP Server
Is the GitLab Documentation MCP server down? Yes. It has given no valid answer since 2026-10-31: not found.
Searchable access to GitLab documentation from multiple repositories with full-text search.
not found down since 2026-10-31 · probed 2026-11-14 · unchanged since 2026-11-07
Error response from daemon: failed to resolve reference "docker.io/nunolima/gitlab-docs-mcp:18.7": docker.io/nunolima/gitlab-docs-mcp:18.7: not found
- Run it
- docker run -i --rm docker.io/nunolima/gitlab-docs-mcp:18.7 (stdio, probed in a container with the network off)
- Host
- docker.io
- Repository
- https://github.com/nunolima/gitlab-docs-mcp
- Registry
- active, updated 2026-02-01 · registry entry
Compare this server with others.
More servers
Other registry entries on docker.io, the ones next to this name; all of them.
- io.github.neverinfamous/mysql-mcp · not found
- PostgreSQL MCP Server io.github.neverinfamous/postgres-mcp-server · not found
- Nhost io.github.nhost/mcp · not probed
- io.github.noisy/noisy-coding · not probed
- io.github.oleksii-donets/simple_mcp · alive
- io.github.oleksii-donets/simple_mcp_http · not probed
- Agent Pattern MCP io.github.olk/agent-pattern-mcp · crashed on start
- Architecture Pattern MCP io.github.olk/architecture-pattern-mcp · not found
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
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
- No valid answer since 2026-10-31, in every probe since then.
- 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.