GitLab MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GITLAB_API_URL | No | Base URL for GitLab API (optional, for self-hosted instances) | https://gitlab.com/api/v4 |
| GITLAB_PERSONAL_ACCESS_TOKEN | Yes | Your GitLab personal access token with required permissions (api, read_api, read_repository, write_repository) |
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 |
|---|---|
| create_or_update_fileC | Create or update a single file in a GitLab project |
| search_repositoriesB | Search for GitLab projects |
| create_repositoryC | Create a new GitLab project |
| get_file_contentsB | Get the contents of a file or directory from a GitLab project |
| push_filesC | Push multiple files to a GitLab project in a single commit |
| create_issueB | Create a new issue in a GitLab project |
| create_merge_requestB | Create a new merge request in a GitLab project |
| fork_repositoryB | Fork a GitLab project to your account or specified namespace |
| create_branchB | Create a new branch in a GitLab project |
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 9 tools
Each tool targets a distinct resource or action (branch, issue, merge request, file, repository, fork, search) with no overlapping purposes.
All tool names follow a consistent verb_noun pattern (e.g., create_branch, get_file_contents), with only 'create_or_update_file' being slightly longer but still consistent.
9 tools is well-scoped for a GitLab server, covering core operations without being excessive or insufficient.
Covers essential create/read operations but lacks explicit update/delete for issues, merge requests, and branches, which agents may need to work around.