Home / MCP registry index / Topics / GitLab
GitLab MCP servers, with their tools checked
Every server in the official MCP registry that mentions GitLab, with a public endpoint, read the way an MCP client reads it and checked for tool poisoning. The list updates as the registry does, and each server is read again every week.
3 listed. We have read the tools of 0 so far; the others want credentials first, could not be reached, or are still waiting for their first read.
These servers act inside an account you own, usually with a token you give them. Prefer the narrowest access the tools need, and check which tools can send, post or delete.
| com.gitlab/mcp com.gitlab/mcp | needs credentials to list tools 2026-10-22 |
| Gitlab io.github.pipeworx-io/gitlab | not read yet |
| Gitlab Public io.github.pipeworx-io/gitlab-public | not read yet |
Choosing one
Open a server's page to see the tools it advertises, whether it sets instructions for the model, and our latest read. A clean read means our rules found nothing, not that a server is harmless; still check what access it asks for. To check one that is not listed, paste its URL into the free MCP server check.
Related: GitHub · Notion · Slack · Discord · Email · Calendar · Google Workspace · Jira and Confluence · all topics