io.github.mshegolev/gitlab-ci-mcp
gitlab_ci_mcp
Is the io.github.mshegolev/gitlab-ci-mcp MCP server down? No. Installed with mcp<2, it started and listed its tools on 2026-11-06.
GitLab CI/CD MCP — pipelines, jobs, schedules, MRs, files. Any GitLab (SaaS or self-hosted).
needs mcp<2 probed 2026-11-14 · unchanged since 2026-11-06
A plain install of the package stops at the import below. These tool definitions are from a second install with mcp<2, started in a container with the network off, on 2026-11-06.
MCP error -32000: Connection closed ModuleNotFoundError: No module named 'mcp.server.fastmcp'. This is mcp 2.x, where FastMCP was renamed to MCPServer (from mcp
- Run it
- uvx --with 'mcp<2' gitlab-ci-mcp@0.5.1 (stdio, probed in a container with the network off)
- Host
- pypi.org
- Reports itself as
- gitlab_ci_mcp 1.30.0
- Capabilities
- experimental, prompts, resources, tools
- Repository
- https://github.com/mshegolev/gitlab-ci-mcp
- Registry
- active, updated 2026-04-17 · registry entry
- Changes
- 2 recorded, reachable in 0 of them. A row is added when the result, the tool count or the cost changes.
Most expensive tools
Estimates with the o200k_base tokenizer.
| Tool | o200k estimate | Share of this server |
|---|---|---|
| gitlab_list_pipelines | 522 | 8 % |
| gitlab_get_job_log | 511 | 7 % |
| gitlab_create_merge_request | 432 | 6 % |
| gitlab_create_schedule | 422 | 6 % |
| gitlab_update_schedule | 422 | 6 % |
Compare this server with others.
More servers
Other registry entries on pypi.org, the ones next to this name; all of them.
- io.github.mrnh/rigor-mcp · alive
- io.github.mscott9160-web/achlens · crashed on start
- Audio MCP io.github.mshark1/audio-mcp · alive
- io.github.mshegolev/allure-testops-mcp · alive
- io.github.mshegolev/harbor-registry-mcp · needs mcp<2
- io.github.mshegolev/jaeger-mcp · needs mcp<2
- io.github.mshegolev/kibana-mcp · needs mcp<2
- io.github.mshegolev/prometheus-mcp · needs mcp<2
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-06 08:38 | needs mcp<2 | 2.0 s | 23 | 12k | 6.9k |
| 2026-10-16 06:28 | crashed on start |
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 imports FastMCP from mcp.server.fastmcp. mcp 2.0, the Python SDK of 28 July 2026, renamed FastMCP to MCPServer, and the package asks for mcp with no upper bound, so a plain install (uvx, pip) gets mcp 2.x and the server stops at the import. Installed with mcp<2, it starts and lists its tools. The fix for the publisher: pin mcp<2 in the dependencies, for example mcp>=1.2,<2, and publish a new version, or move to MCPServer as the SDK's migration guide says. Until then, run it with uvx --with 'mcp<2'.
The cause and the fix, with the code before and after: ModuleNotFoundError: No module named 'mcp.server.fastmcp'