mcp-gitlab
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GITLAB_URI | No | Full GitLab instance URI (e.g., https://gitlab.your-company.com) | |
| GITLAB_HOST | No | GitLab instance hostname (e.g., gitlab.com or gitlab.your-company.com) | |
| GITLAB_TOKEN | Yes | GitLab personal access token |
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| glab_versionA | Returns 'glab --version' text to verify CLI presence |
| gitlab_issues_listC | List issues for a project using glab issue list |
| gitlab_mrs_listC | List MRs for a project using glab mr list |
| gitlab_mr_createC | Create an MR using GitLab REST API via glab api |
| gitlab_pipelines_listC | List pipelines for a project using GitLab REST via |
| gitlab_apiC | Call GitLab REST endpoints with glab api (method, path, fields, headers) |
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 6 tools
Each tool has a clearly distinct purpose: generic API call, list issues, create MR, list MRs, list pipelines, and version check. No ambiguity between them.
Most tools follow a 'gitlab_<resource>_<action>' pattern, but 'gitlab_api' and 'glab_version' deviate in prefix and structure, creating inconsistency.
Six tools is reasonable for a GitLab server covering basic operations, though it could benefit from a few more like issue creation or MR merge.
The toolset covers listing issues, MRs, and pipelines, and creating MRs, but lacks full CRUD for issues and MRs. The generic gitlab_api partially fills gaps, but agents need endpoint knowledge.