MCP GitLab Usage

Binding rules for GitLab MCP tool invocation. Tool schemas and detailed flows live in references — read them before calling tools.

Harness discovery

See ../../ns-harness/references/harness-discovery.md. For GitLab product config (status labels, project ids), read {product_root}/docs/context/gitlab-sync-config.md when it exists.

FIRST ACTION (critical)

When the human asks for requirements, planning, or issues in GitLab:

1. Your first action must be start_execution_planning with inferred arguments. Do not output planning text, RF suggestions, or issue descriptions before a tool response.
2. If MCP tools are unavailable: Say exactly that GitLab MCP is not available in this context. Do not output payloads that cannot be executed.

First access and version check

When connecting to a GitLab MCP server that exposes get_mcp_gitlab_skill: