gitlab-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GITLAB_URL | No | GitLab instance URL (defaults to https://gitlab.com) | https://gitlab.com |
| GITLAB_TOKEN | No | Your GitLab Personal Access Token (if using personal token auth) | |
| GITLAB_OAUTH_TOKEN | No | Your GitLab OAuth2 Token (if using OAuth2 auth) |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_projectsB | List GitLab projects accessible to the authenticated user. |
| list_groupsA | List GitLab groups accessible to the authenticated user. |
| list_group_projectsB | List all projects within a specific GitLab group. |
| get_user_infoA | Get information about the authenticated user. |
| search_repositoriesB | Search for GitLab repositories by name, description, or keywords. |
| get_repository_detailsC | Get detailed information about a specific GitLab repository. |
| read_repository_codeB | Read the complete code structure and content of a repository with filtering options. |
| read_repository_fileB | Read the content of a specific file from a GitLab repository. |
| list_merge_requestsC | List merge requests for a GitLab repository. |
| get_merge_request_analyticsB | Calculate merge request lifetime analytics for a GitLab repository. |
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 10 tools
Each tool targets a distinct resource or aspect: user info, groups, projects, merge requests, code reading, and search. There is no functional overlap between tools.
All tools follow a consistent verb_noun snake_case pattern (e.g., get_, list_, read_, search_), making it predictable for an agent to infer behavior.
With 10 tools covering user, group, project, merge request, and code reading operations, the set is well-scoped for a GitLab-focused server without being overwhelming.
The tool set is read-only and lacks any mutation capabilities (create, update, delete, merge) for repositories, groups, or merge requests, which are essential for GitLab workflows.