Project records
Access projects, issues and merge requests.
Documentation ↗MCP server / developer tools / source-linked
GitLab MCP Server
Current official GitLab MCP server built into GitLab at /api/v4/mcp; seed standalone repo is stale identity. Use this record to separate documented interface facts from proposed evaluation steps, and preserve the checked date with the source links when the provider changes its setup.
Before you choose.
Identify the implementation and the job it supports.
Which implementation is this?
Current official GitLab MCP server built into GitLab at /api/v4/mcp; seed standalone repo is stale identity. Use this record to separate documented interface facts from proposed evaluation steps, and preserve the checked date with the source links when the provider changes its setup.
Implementation source ↗
Current official GitLab MCP server built into GitLab at /api/v4/mcp; seed standalone repo is stale identity. Use this record to separate documented interface facts from proposed evaluation steps, and preserve the checked date with the source links when the provider changes its setup.
Implementation source ↗
Current official GitLab MCP server built into GitLab at /api/v4/mcp; seed standalone repo is stale identity. Use this record to separate documented interface facts from proposed evaluation steps, and preserve the checked date with the source links when the provider changes its setup.
Setup and connection.
The documented interface, authentication and installation path.
- Connection / transport
- HTTP; stdio via mcp-remote
- Authentication
- OAuth dynamic client registration and user authorization.
Enable MCP for instance/group, connect to /api/v4/mcp and complete OAuth.
Setup reference ↗What it actually exposes.
Concrete capabilities with maintainer sources.
CI evidence
Read pipelines, jobs and artifacts.
Documentation ↗Toolsets
Limit the tools returned by the instance.
Documentation ↗Evidence and method.
What was checked and what was not tested.
HOW
Source method
Public maintainer documentation and repositories. This is not a hands-on product review.
WHEN
Last checked 2026-10-01
Setup examples are documented examples. Suggested trials and comparison advice are editorial guidance.
Sources support the adjacent factual statements. A source review does not establish uptime, performance, security or current account eligibility. Read the editorial policy.
Try a specific task.
A bounded evaluation you can reproduce in your own environment.
Explain an MR pipeline failure (proposed; not tested)
Suggested evaluation, not an observed test result.
- Record instance version and returned tools.
- Retrieve MR changes and failed job evidence.
- Draft linked diagnosis without mutation.
What to inspect: Version-specific evidence; proposed, not run.
Workflow reference ↗Permissions and limitations.
Read these constraints before granting access.
Feature is labeled beta and tool availability follows GitLab release.
Boundary reference ↗Editorial inference: confirm tools/list before using examples from later releases.
Boundary reference ↗Decide by workflow.
Make the expected output explicit before you connect.
Version-specific evidence; proposed, not run.
Keep the task inputs, tool calls, output and any errors together when you evaluate. The trial above is a proposal, not a recorded result.
Compare the alternatives.
Specific reasons to choose another route, with the tradeoff shown.
| Alternative | Choose it when | Tradeoff |
|---|---|---|
| GitHub MCP Server | Editorial inference: source is GitHub. | Different platform semantics. Documentation ↗ |
| Git MCP Server | Editorial inference: task is local checkout. | No hosted MR/CI data. Documentation ↗ |
Questions before setup.
Answers specific to this implementation.
Why is a tool missing?
Check version, enabled features and tools/list.
Documentation ↗
How authenticate?
Use the browser OAuth flow after adding the endpoint.
Documentation ↗
Source trail.
Maintainer documentation used in this record.