Gitlab MCP Server 874e48dc

MCP开发工具

提供方 FalkoGuderian

开发工具 stdio · 本地进程 Token 社区 / 第三方 Cline
查看接入方式

基于模型上下文协议(MCP)的GitLab自动化服务器,用于简化的项目管理和开发工作流自动化。

一句话选型结论

按资料字段整理

Gitlab MCP Server 874e48dc 属于开发工具类 MCP 服务器,stdio · 本地进程,Token,可直接接入 Cline,有可直接执行的安装命令。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类开发工具 传输方式stdio · 本地进程 鉴权Token 部署方式本地部署
GitHub 星标 1 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

开发工具
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量未标注暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

支持客户端

适用场景

GitLab自动化Python本地部署项目管理工作流自动化问题管理用户管理

安装与配置

stdio · 本地进程 Token
客户端在本机拉起子进程,数据不出本机
pip install mcp

这条命令只是入口,具体启动参数请按官方文档补齐,不要直接照搬到别的服务器。

  1. 1
    准备运行环境

    stdio 服务在本地起进程,需要先装好 Node.js 等运行时,再按安装命令拉取依赖。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后随便调一个只读工具,确认能返回结果,再接入正式流程。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
代码与仓库操作

在对话里直接查代码、提 issue、走 PR,省掉来回切工具。

本地命令与脚本

把构建、测试、格式化这类重复命令交给模型执行。

接口联调与测试

让模型调你的接口、跑一遍用例,快速定位问题。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 有现成的安装命令,不用自己找入口,照着跑就能起服务。
  • 已适配 Cline,换客户端不用重新研究配置。

先想清楚的地方

  • stdio 方式要求本地装好运行时(如 Node.js),换机器要重新装一遍。
  • 使用前要准备好Token对应的凭据,并按最小权限配置。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在开发工具场景里让模型直接调用外部能力的人。
  • 已经在用 Cline 的用户,接入路径最短。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 完全不想在本地装环境的人。
  • 不方便管理密钥或第三方授权的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
Gitlab MCP Server 874e48dc当前 未标注 stdio · 本地进程 本地部署 有 2026-05-17
Git 838e2ec1 12 stdio · 本地进程 本地部署 有 2026-05-17
Markitdown MCP 2c653a5f 1 stdio · 本地进程 本地部署 有 2026-05-17
JavaGuide 未标注 stdio · 本地进程 本地部署 有 2026-04-11
awesome-claude-skills 未标注 stdio · 本地进程 本地部署 有 2026-04-26
Context7 831acf40 未标注 stdio · 本地进程 本地部署 有 2026-05-17

服务器档案

开发工具
字段来自项目仓库与公开索引,中文说明由本站标注
提供方FalkoGuderian上游标注的维护方 FalkoGuderian
分类开发工具本站按上游分类展示
连接方式stdio · 本地进程客户端在本机拉起子进程,数据不出本机
鉴权方式Token远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · 未标注本地安装时用到的包标识与运行时
部署类型本地部署上游给出的部署形态
最近核验2026-05-17上游最后核验时间

详细介绍

8.2 KB
来自项目仓库与上游目录的原文,未做删改

GitLab MCP Server

A comprehensive GitLab automation server built on the Model Context Protocol (MCP) for streamlined project management and development workflow automation.

Overview

The GitLab MCP Server provides a powerful set of tools for automating GitLab operations, enabling seamless integration with development workflows, intelligent task assignment, and hierarchical project management. It supports both admin and non-admin modes with different capability sets based on user permissions.

Features

Core Capabilities

  • Issue Management: Create, assign, close, and reopen issues with intelligent automation
  • User Management: Comprehensive user operations and role-based access control
  • Project Management: Full project lifecycle management with member administration

Installation

Prerequisites

  • Python 3.8 or higher
  • GitLab instance with API access
  • GitLab Personal Access Token with appropriate permissions

Setup Steps

  1. Clone or download the server files:bash # Files needed: # - gitlab-mcp-server.py # - gitlab-mcp-config.json

  2. Install Python dependencies:bash pip install mcp

  3. Configure the server:
    Edit gitlab-mcp-config.json with your GitLab instance details:json { "gitlab_url": "https://your-gitlab-instance.com", "access_token": "your-gitlab-token", "default_project_id": 1, "default_user_id": 1 }

  4. Set environment variables (optional):bash export DEFAULT_GITLAB_PROJECT_ID=1 export DEFAULT_GITLAB_USER_ID=1 export GITLAB_MCP_ADMIN_MODE=false

> Note: gitlab_url and access_token must be configured in the gitlab-mcp-config.json file, not as environment variables.

MCP Configuration

To integrate this GitLab MCP Server with your development environment, add the following configuration to your MCP settings file (typically located at ~/.cline/mcp-settings.json or in your IDE's MCP configuration):```json
{
"mcpServers": {
"gitlab": {
"command": "python",
"args": [
"<base-directory>\gitlab-mcp-server.py"
],
"env": {
"GITLAB_TOKEN": "your-gitlab-token-here",
"GITLAB_URL": "http://localhost",
"DEFAULT_GITLAB_PROJECT_ID": "4",
"DEFAULT_GITLAB_USER_ID": "5",
"GITLAB_MCP_ADMIN_MODE": "false"
},
"autoApprove": [
"list_gitlab_users",
"list_project_issues",
"list_assignee_open_tasks"
],
"disabled": false,
"timeout": 60
}
}
}


### Additional MCP Servers

The configuration also supports additional MCP servers for enhanced functionality:

#### Git Server```json
&quot;github.com/modelcontextprotocol/servers/tree/main/src/git&quot;: {
  &quot;command&quot;: &quot;python&quot;,
  &quot;args&quot;: [&quot;-m&quot;, &quot;mcp_server_git&quot;],
  &quot;autoApprove&quot;: [],
  &quot;disabled&quot;: false,
  &quot;timeout&quot;: 60
}

Search Server```json

"github.com/NightTrek/Serper-search-mcp": {
"command": "node",
"args": ["d:/Projects/mcp/serper-search-server/build/index.js"],
"env": {
"SERPER_API_KEY": "your-serper-api-key",
"OPENROUTER_API_KEY": "your-openrouter-api-key"
},
"autoApprove": [],
"disabled": false,
"timeout": 60
}


### Configuration Options

- **autoApprove**: List of tool names that can be executed without manual approval
- **disabled**: Set to `true` to disable the server
- **timeout**: Request timeout in seconds
- **env**: Environment variables passed to the server process

## Configuration

### Basic Configuration (`gitlab-mcp-config.json`)

| Field | Description | Required |
|-------|-------------|----------|
| `gitlab_url` | Your GitLab instance URL | Yes |
| `access_token` | GitLab Personal Access Token | Yes |
| `default_project_id` | Default project for operations | No |
| `default_user_id` | Default user for assignments | No |

### Access Token Permissions

For full functionality, your GitLab Personal Access Token should have:
- `read_api` - Read access to API
- `read_user` - Read user information
- `read_repository` - Read repository data
- `write_repository` - Write repository data
- `api` - Full API access (for admin operations)

### Admin Mode vs Non-Admin Mode

**Admin Mode** (`admin_mode: true`):
- Full access to all tools
- Can delete issues
- Can manage all projects and users
- Can perform bulk operations

**Non-Admin Mode** (`admin_mode: false`):
- Limited to assignee-related operations
- Can only work with assigned issues
- Cannot delete issues
- Cannot access user management tools

## Available Tools

### Issue Management Tools

#### `list_open_issues`
Get open issues assigned to a specific user.```json
{
  &quot;project_id&quot;: 4,
  &quot;user_id&quot;: 5
}

list_closed_issues

Get closed issues assigned to a specific user.```json
{
"project_id": 4,
"user_id": 5
}


#### `close_issue`
Close a specific issue with optional comment.```json
{
  &quot;project_id&quot;: 4,
  &quot;issue_iid&quot;: 123,
  &quot;comment&quot;: &quot;Issue resolved successfully&quot;
}

reopen_issue

Reopen a closed issue with optional comment.```json
{
"project_id": 4,
"issue_iid": 123,
"comment": "Reopening for additional work"
}


#### `create_bug`
Create a new bug issue with &quot;BUG: &quot; prefix.```json
{
  &quot;project_id&quot;: 4,
  &quot;title&quot;: &quot;Login button not working&quot;,
  &quot;description&quot;: &quot;Users cannot log in when clicking the login button&quot;,
  &quot;labels&quot;: [&quot;bug&quot;, &quot;urgent&quot;],
  &quot;assignee_id&quot;: 5
}

delete_all_project_issues (Admin Only)

Delete all issues in a project.```json
{
"project_id": 4
}


### User Management Tools (Admin Only)

#### `list_gitlab_users`
Get all users in the GitLab instance.

#### `list_project_issues`
Get all issues in a project.

## Usage Examples

### Creating a Bug Report```bash
# Using the MCP server to create a bug
{
  &quot;tool&quot;: &quot;create_bug&quot;,
  &quot;arguments&quot;: {
    &quot;title&quot;: &quot;Authentication failure on mobile devices&quot;,
    &quot;description&quot;: &quot;Users are experiencing login issues when accessing the application from mobile browsers.&quot;,
    &quot;labels&quot;: [&quot;bug&quot;, &quot;mobile&quot;, &quot;authentication&quot;],
    &quot;assignee_id&quot;: 5
  }
}

Managing Issue Lifecycle```bash

Close an issue with a comment

{
"tool": "close_issue",
"arguments": {
"issue_iid": 123,
"comment": "Fixed in commit abc123. Tested on multiple browsers."
}
}


### Getting User Assignments```bash
# List all open issues for a specific user
{
  &quot;tool&quot;: &quot;list_open_issues&quot;,
  &quot;arguments&quot;: {
    &quot;user_id&quot;: 5
  }
}

Development Workflow

  1. Project Planning: Create structured issues and organize them with labels and milestones
  2. Task Assignment: Assign issues to appropriate team members
  3. Progress Tracking: Monitor issue status and completion
  4. Quality Assurance: Use labels and milestones for organization

Error Handling

The server provides comprehensive error handling for:

  • Network Issues: Connection problems with GitLab API
  • Authentication Errors: Invalid or expired tokens
  • Permission Errors: Insufficient permissions for operations
  • Validation Errors: Invalid parameters or missing required fields

Security Considerations

  • Store access tokens securely (environment variables recommended)
  • Use minimal required permissions for tokens
  • Enable admin mode only when necessary
  • Regularly rotate access tokens
  • Monitor API usage and rate limits

Troubleshooting

Common Issues

"GitLab API not configured"
- Ensure gitlab_url and access_token are set in config
- Verify token has required permissions

"No project_id provided"
- Set default_project_id in config or provide in tool arguments
- Verify project exists and is accessible

"Permission denied"
- Check access token permissions
- Verify user has access to specified project
- Consider admin mode requirements

Debug Mode

Enable debug logging by setting environment variable:bash export GITLAB_MCP_DEBUG=true

Contributing

To extend the server with new tools:

  1. Add tool definition in handle_list_tools()
  2. Implement tool logic in handle_call_tool()
  3. Update configuration schema if needed
  4. Add tests and documentation

License

MIT License - feel free to use this project in your own applications.

Support

For issues and questions:
- Check the troubleshooting section
- Verify your GitLab instance configuration
- Ensure all prerequisites are met
- Review access token permissions

常见问题

8 问
答案由本站依据条目字段整理,不引用上游原文
Gitlab MCP Server 874e48dc 怎么安装?

在客户端按下面的安装命令接入:pip install mcp。装完在客户端配置里引用同一个包或端点。

Gitlab MCP Server 874e48dc 怎么在 Cline 里配置?

它的传输方式是stdio · 本地进程,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

Gitlab MCP Server 874e48dc 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

Gitlab MCP Server 874e48dc 需要 API Key 吗?

资料标注需要Token认证,使用前准备好对应凭据,并按最小权限配置。

Gitlab MCP Server 874e48dc 支持哪些客户端?

资料标注支持 Cline;其他客户端只要能配置 MCP Server,也能用同样的命令或地址接入。

Gitlab MCP Server 874e48dc 能提供哪些能力?

资料显示能力标签包括 工作流自动化、Python、Cline、问题管理。具体工具清单以官方文档为准。

Gitlab MCP Server 874e48dc 需要什么运行环境?

属于本地进程,需要在本机装好运行环境。

Gitlab MCP Server 874e48dc 是本地还是远程?

它是本地进程(stdio),由客户端在本机拉起。传输方式为stdio · 本地进程。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 2026-05-17。