gitlab-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GITLAB_API_TOKEN | Yes | Your GitLab personal access token with api or read_api scope | |
| GITLAB_PROJECT_ID | Yes | The GitLab project ID (numeric) | |
| GITLAB_INSTANCE_URL | Yes | The GitLab instance URL (e.g., https://gitlab.com or self-hosted) |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_merge_requestC | Get basic information about a merge request |
| get_merge_request_commitsA | Get all commits in a merge request |
| get_merge_request_diffsA | Get all file changes and diffs in a merge request |
| get_merge_request_discussionsA | Get all discussions and comments on a merge request |
| get_merge_request_approvalsB | Get approval status and information for a merge request |
| get_merge_request_pipelinesA | Get CI/CD pipeline information for a merge request |
| get_merge_request_fullB | Get complete information about a merge request (all data in one call) |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Each tool targets a distinct facet of a merge request (basic info, commits, diffs, discussions, approvals, pipelines, full aggregate), so there is no overlap or ambiguity between them. The 'full' tool is comprehensive but clearly distinguished as a combined superset.
All tools follow the exact same 'get_merge_request_*' pattern, making the naming highly predictable and consistent. The resource and action are clearly identified in every name.
Seven tools is a well-scoped set for a read-only merge request inspection server. Each tool covers a meaningful data aspect without adding unnecessary clutter, and the aggregate 'full' tool reduces the need for more granular additions.
The server thoroughly covers all major data dimensions of an individual merge request, including a 'full' option. The only notable gap is the absence of a list/search tool to discover merge requests, which may require external context to work with.