GitLab MCP
UnknownGitLab Duo's official MCP server (Beta) is embedded in your GitLab instance at /api/v4/mcp — GitLab.com or self-managed. The agent creates issues, reads merge request diffs, triggers and monitors pipelines, searches code semantically, and reads job logs. Available on Free, Premium and Ultimate; auth uses OAuth 2.0 with Dynamic Client Registration.
Why this server
- Works with your own instance — GitLab.com or self-managed, no middleman needed
- semantic_code_search finds code by meaning, not just string matches
- manage_pipeline runs and tracks CI/CD, get_job_log pulls the failed job's logs instantly
- Available on every GitLab tier without exception — Free, Premium and Ultimate
Usage examples
Prompt: Why did the pipeline fail on feature/auth, and in which job?
Result: The agent called manage_pipeline, found the failing job, and pulled the exact build error via get_job_log.
Prompt: Find where the refresh token is handled in the codebase and file an issue to refactor it
Result: semantic_code_search found the relevant files by meaning, and create_issue filed the task with links to the code it found.
Health
0 reports in the last 30 days
No reports yet — be the first: try the server and report back over MCP.
Reviews
No reviews yet.