日本語 | English

[[mcp-gitlab-workflow] は、GitLab の開発を主導する MCP サーバーです。

要件または既存のGitLabの問題を取り、標準化された配信フローを駆動できます。要件分析、問題作成、ブランチング、コーディング、マージリクエストの作成、および問題の更新。 また、カスタムオーケストレーションと微調整制御用のアトミックGitLab APIツールのセットも提供しています。

#1. コア機能

• [workflow_*:一般的な要件をパッケージ化する高レベルなツールが単一のツールコールに流れます
• [[gitlab_*:カスタムオーケストレーションと微調整のためのアトミックGitLab APIツール

WORKFLOW_ISSUE_PROJECT_IDと[WORKFLOW_CODE_PROJECT_ID]で課題やコード配信の対象プロジェクトを構成します。 全構成行列の環境変数セクションを参照してください。

###ワークフローツール

• [workflow_requirement_to_issue:要件を分析し、GitLabの問題を作成します
• [workflow_review_mr_post_comment: ターゲットマージリクエストを見直し、レビューコメントを投稿する
• [workflow_issue_to_delivery:既存の問題から始まり、ブランチ→コード変更→MR→問題コメント→問題ログ

mcp-gitlab-workflow

English | 简体中文

mcp-gitlab-workflow is an MCP server for issue-driven GitLab development.

It can take a requirement or an existing GitLab issue and drive a standardized delivery flow: requirement analysis, issue creation, branching, coding, merge request creation, and issue updates. It also provides a set of atomic GitLab API tools for custom orchestration and fine-grained control.

1. Core Capabilities

• workflow_*: higher-level tools that package common requirement-to-delivery flows into a single tool call
• gitlab_*: atomic GitLab API tools for custom orchestration and fine-grained control

Target projects for issues and code delivery are configured with WORKFLOW_ISSUE_PROJECT_ID and WORKFLOW_CODE_PROJECT_ID. See the environment variable section below for the full configuration matrix.

Workflow Tools

• workflow_requirement_to_issue: analyze a requirement and create a GitLab issue
• workflow_review_mr_post_comment: review a target merge request and post a review comment
• workflow_issue_to_delivery: start from an existing issue and complete branch -> code change -> MR -> issue comment -> issue log
• workflow_requirement_to_delivery: run the full end-to-end flow from a requirement

Atomic GitLab Tools

Issue tools fall back to WORKFLOW_ISSUE_PROJECT_ID by default, while code and merge request tools fall back to WORKFLOW_CODE_PROJECT_ID.

• Users and labels: gitlab_get_current_user, gitlab_list_labels, gitlab_create_label, gitlab_update_label, gitlab_delete_label
• Issues: gitlab_create_issue, gitlab_get_issue, gitlab_get_issue_notes, gitlab_add_issue_comment, gitlab_get_issue_images
• Repository: gitlab_create_branch, gitlab_get_file, gitlab_commit_files, gitlab_upload_project_file
• Merge requests: gitlab_get_merge_request, gitlab_get_mr_notes, gitlab_create_merge_request, gitlab_create_mr_note, gitlab_get_mr_changes, gitlab_approve_mr, gitlab_unapprove_mr

2. Example

Using workflow_requirement_to_delivery as an example, it is best to explicitly name the tool in your prompt or wrap it in a higher-level custom instruction / skill so the LLM can reliably choose the intended workflow.

Input

Use workflow_requirement_to_delivery to add a forum interaction feature

Result

The workflow can automatically complete the flow below:

requirement analysis -> issue creation -> branch -> code change -> MR -> issue update

(1) Issue creation

(2) Code changes and MR submission based on the issue

(3) Issue comment