GitLab.com远程HTTP MCP需适用OAuth/细粒度PAT及group允许;只描述project/issue/MR读取,未连接。
调用方式 / profile:gitlab-mcp-server-documentation · 组件版本:documentation-sha256:bc9634b6b3f21cb5d8111d0ff357b524fa52cb8d71d6fa65b3913e0d83d00a9d · 引用此版本与调用方式
已记录条件
- invocation_mode = api:支持。Supported within this profile and component version. 依据:gitlab-mcp-server-documentation-e1
- execution_location = remote:支持。Supported within this profile and component version. 依据:gitlab-mcp-server-documentation-e1
- auth_required = true:支持。Supported within this profile and component version. 依据:gitlab-mcp-server-documentation-e2
入口与前提
- 协议
- MCP over direct HTTP
- 认证
- OAuth mcp scope,或MCP tool resource+Execute的细粒度PAT;旧PAT/project/group token不适用
- 价格是否查明
- unknown
- 配额是否查明
- unknown
https://gitlab.com/api/v4/mcp
- 仅官方文档声明,配方proposed;本站未连接、注册、调用第三方工具或核验实际账户。
- GitLab.com须group允许,Self-Managed/Dedicated须instance允许;DCR关闭时需预注册app/相应管理角色。
- 基础MCP列Free/Premium/Ultimate;Duo/安全工具另受credits/seat/license等条件,不宣传全免费或自动付费。
- 直接HTTP不要求本地server安装;stdio的mcp-remote路径才另需Node,未采用。
- 文档限流依方案、feature flags和共享额度;实际账户/实例值、费用未知;列出工具不授予访问。
配方 gitlab-mcp-server-documentation-recipe · 修订 1
所需调用能力:
- read_authorized_gitlab_metadata_via_mcp
运行前提:
- 仅官方文档声明,配方proposed;本站未连接、注册、调用第三方工具或核验实际账户。
- GitLab.com须group允许,Self-Managed/Dedicated须instance允许;DCR关闭时需预注册app/相应管理角色。
- 基础MCP列Free/Premium/Ultimate;Duo/安全工具另受credits/seat/license等条件,不宣传全免费或自动付费。
- 直接HTTP不要求本地server安装;stdio的mcp-remote路径才另需Node,未采用。
- 文档限流依方案、feature flags和共享额度;实际账户/实例值、费用未知;列出工具不授予访问。
使用步骤:
- 准备已获授权的最小输入,核对本profile的适用范围、认证与费用;不填私人信息或凭据到公开示例。
- 仅候选:在已获准HTTP MCP客户端使用https://gitlab.com/api/v4/mcp和适用认证;先发现有权限的只读工具,本站不注册OAuth、不连接、不执行。
- 未来获准调用后核对HTTP/MCP状态、返回结构与请求条件,保留缺项/限流/权限错误;本次没有执行此步骤。
- 输入约定
- 已允许MCP的GitLab.com group、适用OAuth/细粒度PAT;准确基础工具名/input schema须由授权server发现。
- 输出约定
- 文档声明可读取project/issue/MR数据;没有完整基础tool schema,不捏造工具名/结果模型,也不证明pipeline工具。
- 成功检查
- 未来核对endpoint、token类别/scope、group允许及server schema;只使用已授权只读工具,401/403时停止。
- 失败与回退
- 条件不满足、认证/限流/结构错误即停止该调用并保留unknown;不切换付费服务、不猜工具名、不执行写操作。
适用证据
gitlab-mcp-server-documentation-e1 · 来源文档声明
- 原文定位
- .local/deep-cards-v1/api-expansion-20261024-01/sources/gitlab-mcp-server-documentation.txt:L104-L127
- 来源版本
- documentation-sha256:bc9634b6b3f21cb5d8111d0ff357b524fa52cb8d71d6fa65b3913e0d83d00a9d
- 内容摘要
- bc9634b6b3f21cb5d8111d0ff357b524fa52cb8d71d6fa65b3913e0d83d00a9d
- 采集时间
- 2026-10-24T04:07:12.6655686+00:00
The GitLab MCP server supports two transport types: HTTP transport (recommended): Direct connection without additional dependencies. stdio transport with mcp-remote : Connection through a proxy (requires Node.js). Common AI tools support the JSON configuration format for the mcpServers key and provide different methods to configure the GitLab MCP server settings. To limit which tools the server returns, see Select tool groups (toolsets). HTTP transport (recommended) History Introduced in GitLab 18.6. Tool prefixing added in GitLab 18.11. To configure the GitLab MCP server by using HTTP transport, use this format: Replace <gitlab.example.com> with: On GitLab Self-Managed, your GitLab instance URL. On GitLab.com, gitlab.com . json { "mcpServers": { "GitLab": { "type": "http", "url": "https://<gitlab.example.com>/api/v4/mcp"
覆盖条件:invocation_mode=api; execution_location=remote
gitlab-mcp-server-documentation-e2 · 来源文档声明
- 原文定位
- .local/deep-cards-v1/api-expansion-20261024-01/sources/gitlab-mcp-server-documentation.txt:L84-L101
- 来源版本
- documentation-sha256:bc9634b6b3f21cb5d8111d0ff357b524fa52cb8d71d6fa65b3913e0d83d00a9d
- 内容摘要
- bc9634b6b3f21cb5d8111d0ff357b524fa52cb8d71d6fa65b3913e0d83d00a9d
- 采集时间
- 2026-10-24T04:07:12.6655686+00:00
The GitLab MCP server accepts the following tokens: An OAuth access token with the mcp scope. MCP clients get this token through the OAuth flow when they connect, either with dynamic client registration or with a pre-registered OAuth application. A fine-grained personal access token with the MCP tool resource and the Execute permission. These tokens cannot have the mcp scope, so the GitLab MCP server rejects them, even with scopes such as api : Legacy personal access tokens Project access tokens Group access tokens If you use one of these tokens, the GitLab MCP server returns 403 Forbidden with the insufficient_scope error. The response names the mcp scope, which you can’t add to these tokens.
覆盖条件:auth_required=true
结构化配方尚未提供或不适用于本版本;旧用法文字保留,连接与执行结果未知。