GitLab
Repository and project management through GitLab's API
GitLab MCP Server
MCP Server for the GitLab API, enabling project management, file operations, and more.
Features
- Automatic Branch Creation: When creating/updating files or pushing changes, branches are automatically created if they don't exist
- Comprehensive Error Handling: Clear error messages for common issues
- Git History Preservation: Operations maintain proper Git history without force pushing
- Batch Operations: Support for both single-file and multi-file operations
Tools
create_or_update_file- Create or update a single file in a project
- Inputs:
project_id(string): Project ID or URL-encoded pathfile_path(string): Path where to create/update the filecontent(string): Content of the filecommit_message(string): Commit messagebranch(string): Branch to create/update the file inprevious_path(optional string): Path of the file to move/rename
- Returns: File content and commit details
push_files- Push multiple files in a single commit
- Inputs:
project_id(string): Project ID or URL-encoded pathbranch(string): Branch to push tofiles(array): Files to push, each withfile_pathandcontentcommit_message(string): Commit message
- Returns: Updated branch reference
search_repositories- Search for GitLab projects
- Inputs:
search(string): Search querypage(optional number): Page number for paginationper_page(optional number): Results per page (default 20)
- Returns: Project search results
create_repository- Create a new GitLab project
- Inputs:
name(string): Project namedescription(optional string): Project descriptionvisibility(optional string): 'private', 'internal', or 'public'initialize_with_readme(optional boolean): Initialize with README
- Returns: Created project details
get_file_contents- Get contents of a file or directory
- Inputs:
project_id(string): Project ID or URL-encoded pathfile_path(string): Path to file/directoryref(optional string): Branch/tag/commit to get contents from
- Returns: File/directory contents
create_issue- Create a new issue
- Inputs:
project_id(string): Project ID or URL-encoded pathtitle(string): Issue titledescription(optional string): Issue descriptionassignee_ids(optional number[]): User IDs to assignlabels(optional string[]): Labels to addmilestone_id(optional number): Milestone ID
- Returns: Created issue details
create_merge_request- Create a new merge request
- Inputs:
project_id(string): Project ID or URL-encoded pathtitle(string): MR titledescription(optional string): MR descriptionsource_branch(string): Branch containing changestarget_branch(string): Branch to merge intodraft(optional boolean): Create as draft MRallow_collaboration(optional boolean): Allow commits from upstream members
- Returns: Created merge request details
fork_repository- Fork a project
- Inputs:
project_id(string): Project ID or URL-encoded pathnamespace(optional string): Namespace to fork to
- Returns: Forked project details
create_branch- Create a new branch
- Inputs:
project_id(string): Project ID or URL-encoded pathbranch(string): Name for new branchref(optional string): Source branch/commit for new branch
- Returns: Created branch reference
Setup
Personal Access Token
Create a GitLab Personal Access Token with appropriate permissions:
- Go to User Settings > Access Tokens in GitLab
- Select the required scopes:
apifor full API accessread_apifor read-only accessread_repositoryandwrite_repositoryfor repository operations
- Create the token and save it securely
Usage with Claude Desktop
Add the following to your claude_desktop_config.json:
Docker
{
"mcpServers": {
"gitlab": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"-e",
"GITLAB_PERSONAL_ACCESS_TOKEN",
"-e",
"GITLAB_API_URL",
"mcp/gitlab"
],
"env": {
"GITLAB_PERSONAL_ACCESS_TOKEN": "<YOUR_TOKEN>",
"GITLAB_API_URL": "https://gitlab.com/api/v4" // Optional, for self-hosted instances
}
}
}
}
NPX
{
"mcpServers": {
"gitlab": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-gitlab"
],
"env": {
"GITLAB_PERSONAL_ACCESS_TOKEN": "<YOUR_TOKEN>",
"GITLAB_API_URL": "https://gitlab.com/api/v4" // Optional, for self-hosted instances
}
}
}
}
Build
Docker build:
docker build -t vonwig/gitlab:mcp -f src/gitlab/Dockerfile .
Environment Variables
GITLAB_PERSONAL_ACCESS_TOKEN: Your GitLab personal access token (required)GITLAB_API_URL: Base URL for GitLab API (optional, defaults tohttps://gitlab.com/api/v4)
License
This MCP server is licensed under the MIT License. This means you are free to use, modify, and distribute the software, subject to the terms and conditions of the MIT License. For more details, please see the LICENSE file in the project repository.
Related
More Developer Tools MCP servers
Git
MCP server
Local Git operations including commits, diffs, and repository management
GitHub
GitHub
GitHub’s official MCP server for repositories, code, issues, pull requests, Actions, and security workflows.
Wavegrain
MCP server
Curated TikTok slideshows and Instagram carousels for your brand on autopilot. Hosted remote MCP server at https://wavegrain.com/api/mcp (Streamable HTTP, OAuth).
Wavegrain
MCP server
Hosted MCP server for Wavegrain: curated TikTok slideshows and Instagram carousels for your brand on autopilot. Agents read your brand, make slideshows in its voice with your photos, edit slides, schedule them and export, within a credit limit you set. Server: https://wavegrain.com/api/mcp (Streamable HTTP, OAuth). Docs: https://wavegrain.com/mcp
链小知区块链
MCP server
Chinese blockchain research through eight read-only MCP tools: knowledge and methodology, tool directory, usage guides, latest news, search, hot topics, event timelines and daily briefs. Hosted Streamable HTTP endpoint: https://lianxiaozhi.com/api/mcp. No API key, token or account required. News search covers the last 7 days; knowledge does not have that window. Source links and dates support verification. No wallet access or transaction execution. Affiliated submission by the content-operations team of 链小知区块链; this listing makes no claim that the hosted server code is open source.
Keep Mac Awake
MCP server
Keep Mac Awake MCP server lets an AI agent keep a MacBook with Apple silicon awake with the lid closed while long work runs: a test suite, a migration, an agent run you check from your phone. Three tools call the keepmacawake command of the Keep Mac Awake app on your Mac: status, start (1 to 168 hours, or no time limit after the user agrees) and stop. The agent asks before a session without a time limit and before the first session, never starts a second one over a running session, and tells you when the app needs AC power or a purchase. Local only: no network connection, no telemetry, and the Mac ID never reaches the conversation. Needs the Keep Mac Awake app (any Mac with Apple silicon and macOS 26 or later, keepmacawake.com), a paid app with a free trial. Install: npx -y keepmacawake-mcp (Official MCP Registry: com.keepmacawake/mcp).