GitLab MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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_current_user | 获取当前 GitLab 用户信息 |
| get_project_ids | 搜索项目并获取项目 ID 映射 |
| create_merge_request | 创建合并请求 (MR) |
| create_merge_request_to_public | 创建从个人仓库到公共仓库的合并请求 |
| merge_branch | 执行分支合并 |
| get_merge_request_statusC | 获取合并请求状态 |
| close_merge_request | 关闭合并请求 |
| wait_for_mergeable_status | 等待 MR 状态变为可合并 |
| get_project | 获取项目详情 |
| get_repository_branches | 获取仓库所有分支 |
| create_branch | 创建新分支 |
| delete_branch | 删除分支 |
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 1 tool
With only one tool, there is no possibility of ambiguity or overlap.
A single tool trivially maintains naming consistency; there are no inconsistencies to assess.
One tool for a GitLab server is extremely thin; GitLab's broad feature set requires many more tools for meaningful coverage.
The server only exposes a merge request status check, missing all other essential GitLab operations such as issue, repository, and pipeline management.