GitLab MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GITLAB_URL | No | The URL of your GitLab instance | https://gitlab.com |
| GITLAB_PROJECT_ID | Yes | The GitLab project ID (numeric ID, not project name) | |
| GITLAB_ACCESS_TOKEN | Yes | GitLab access token with read_api permissions |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| logging | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_merge_requestsC | List merge requests for the GitLab project |
| get_merge_request_reviewsC | Get reviews and discussions for a specific merge request |
| get_merge_request_detailsB | Get detailed information about a specific merge request |
| get_merge_request_pipelineA | Get the last pipeline data for a specific merge request, including all jobs and their statuses. Returns job IDs that can be used with get_job_log to fetch detailed output. |
| get_merge_request_test_reportA | Get structured test report for a merge request with specific test failures, error messages, and stack traces. Shows the same test data visible on the GitLab MR page. Best for debugging test failures. |
| get_pipeline_test_summaryA | Get test summary for a merge request - a lightweight overview showing pass/fail counts per test suite. Faster than full test report. Great for quick status checks. |
| get_job_logA | Get the trace/log output for a specific pipeline job. Perfect for debugging failed tests and understanding CI/CD failures. |
| get_branch_merge_requestsC | Get all merge requests for a specific branch |
| reply_to_review_commentC | Reply to a specific discussion thread in a merge request review |
| create_review_commentC | Create a new discussion thread in a merge request review |
| resolve_review_discussionC | Resolve or unresolve a discussion thread in a merge request review |
| get_commit_discussionsC | Get discussions and comments on commits within a specific merge request |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/FitoDomik/gitlab-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server