[Discovery] mcp/gitlab - GitLab API Integration

Open
#7 0 comments 0 reactions 0 assignees View on GitHub

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
Domain
api, devops, tooling

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

category/git phase/discovery transport/http-wrapped type/research

Project Association

This issue tracks the gitlab MCP server in the core profile.

Server Details
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 projects
  • get_project: Get project details
  • list_branches: List branches in a project
  • get_file_contents: Read file contents from a repository
  • create_or_update_file: Create or update a file
  • push_files: Push multiple files in a single commit
  • create_branch: Create a new branch
  • create_merge_request: Create a new merge request
  • list_merge_requests: List merge requests
  • get_merge_request: Get merge request details
  • merge_merge_request: Merge a merge request
  • create_issue: Create a new issue
  • list_issues: List issues in a project
  • get_issue: Get issue details
  • update_issue: Update an existing issue
  • add_issue_comment: Add comment to an issue
  • list_pipelines: List CI/CD pipelines
  • get_pipeline: Get pipeline details
  • trigger_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

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from aRustyDev/mcp

All issues in aRustyDev/mcp

Similar issues

More Backend & API Design issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.