[Discovery] mcp/gitlab - GitLab API Integration
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- docker, node.js, typescript
Research direction
Start with the upstream src/gitlab implementation and this repository’s gitlab.dockerfile, then inspect how the HTTP wrapper is configured. The tracked work includes documenting all tools, checking HADOLint compliance, testing self-hosted GitLab, and evaluating a Rust rewrite; completion is not defined as one bounded change.
Written by the indexing model from the issue text.
Description
Project Association
This issue tracks the gitlab MCP server in the core profile.
Server Details
- Name: gitlab
- Source: https://github.com/modelcontextprotocol/servers/tree/main/src/gitlab
- Docker Hub: https://hub.docker.com/r/mcp/gitlab
- Category: git
- Language: TypeScript/Node.js
Transport Status
- Current: stdio only (upstream)
- Implementation: HTTP-wrapped via supergateway
- Docker Image:
gitlab-mcp:http(custom build)
Tools Provided
search_repositories: Search for GitLab projectsget_project: Get project detailslist_branches: List branches in a projectget_file_contents: Read file contents from a repositorycreate_or_update_file: Create or update a filepush_files: Push multiple files in a single commitcreate_branch: Create a new branchcreate_merge_request: Create a new merge requestlist_merge_requests: List merge requestsget_merge_request: Get merge request detailsmerge_merge_request: Merge a merge requestcreate_issue: Create a new issuelist_issues: List issues in a projectget_issue: Get issue detailsupdate_issue: Update an existing issueadd_issue_comment: Add comment to an issuelist_pipelines: List CI/CD pipelinesget_pipeline: Get pipeline detailstrigger_pipeline: Trigger a new pipeline
Docker Status
- Official image:
mcp/gitlab - Custom wrapper:
gitlab.dockerfile - HADOLint: Not checked
Notes
- Supports self-hosted GitLab via
GITLAB_API_URL - Comprehensive GitLab API coverage including CI/CD
- Requires
GITLAB_PERSONAL_ACCESS_TOKEN
Tracking
- Document all tools comprehensively
- HADOLint compliance check
- Test with self-hosted GitLab
- Consider Rust rewrite
- Dominant language
- Just
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from aRustyDev/mcp
-
Difficulty 2/5 1-3 hours Newbie friendliness 55/100
-
category/workflow phase/discovery transport/http-streamed type/research
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
category/workflow phase/discovery transport/http-streamed type/research
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
category/docs phase/discovery transport/http-streamed type/research
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
category/workflow phase/discovery transport/http-streamed type/research
Difficulty 4/5 3-5 days Newbie friendliness 25/100
Similar issues
-
bug clawsweeper:linked-pr-open clawsweeper:needs-live-repro clawsweeper:no-new-fix-pr impact:message-loss issue-rating: 🐚 platinum hermit P2 regression
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
AXERA-TECH/ax-llm#77 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
games-on-whales/wolf#509 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100