
Gitlab Ci Break Lint
io.github.jmshinhwaPublished by GitHub account jmshinhwav1.0.1Updated Oct 24, 2026
Names the .gitlab-ci.yml lines your runner will reject after the next GitLab major upgrade
The publisher's own server: Gitlab
Overview
A local MCP server that flags lines in a .gitlab-ci.yml file that a GitLab runner will reject after the next major upgrade.
- What you can do
- It inspects GitLab CI configuration and reports the specific lines that the runner will reject after the next GitLab major upgrade, so an assistant can point out what needs changing. The registry description states it names those lines. The manifest lists no tools, so the exact tool surface is not documented here.
- When to use it
- Worth adding when you maintain GitLab CI pipelines and want to find upgrade-breaking configuration before a GitLab major version lands. Useful for reviewing an existing .gitlab-ci.yml during upgrade preparation.
- Requirements
- Runs as a local process on the user's machine via npx from the npm package @readystack/gitlab-ci-break-lint. Desktop only; no web executable. No authentication, environment variables, or headers are declared.
Installation
In SourceWeft
- Open Gitlab Ci Break Lint in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
readystack-themes
Made by ReadyStack · free calculators and templates at getreadystack.com VS Code themes by ReadyStack
Source: README.md at commit ee1c884
Tools
0Version history
1- v1.0.1LatestSep 23, 2026
Score
40% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Declare a license in the repository or the registry entry.
Other Gitlab integrations
Gitlab
com.gitlabOfficial publisher
Gitlab's hosted MCP server, published by gitlab.com; credential required; Streamable HTTP.

GitLab MCP Server
Published by GitHub account sumirati
A local GitLab MCP server that lets an assistant read and manage projects, branches, commits, merge requests, issues and CI/CD pipelines on GitLab.com or self‑h

Gitlab Mcp
Published by GitHub account mmedum
Local stdio MCP server that lets an assistant work inside your gitlab.com projects as you: issues, merge requests, reviews, repository and CI.

Gitlab Mcp
Published by GitHub account mrfentmen
Lets an assistant look up public GitLab projects and users without any API key.
GitLab MCP Server
Published by GitHub account zereight
Local GitLab MCP server that lets an assistant work with projects, merge requests, issues, pipelines, wiki and releases through the GitLab API.