Get merge request approval details including approvers. Inspect approval rules and approvers before merging. Use approve_merge_request to change approval state.

Search for GitLab projects. If the identifier is known, use a typed get or list tool.

Get contents of a file or directory from a GitLab project.

Create a new issue. Open a new issue. Use update_issue for an existing issue and create_issue_note for discussion.

Create a new merge request. Open a merge request from an existing source branch to a target. Use update_merge_request after it exists.

Get branch details (commit, protection status). To find resources, use the matching list or search tool.

List branches in project with search filter. For one known resource, use the matching get tool.

Get details of a merge request (merge_request_iid or source_branch required). Set include_summaries=true for deployment/commit/approval summaries. To find resources, use the matching list or search tool.

Get the changes/diffs of a merge request (merge_request_iid or source_branch required). To find resources, use the matching list or search tool.

List changed file paths in a merge request without diff content (merge_request_iid or source_branch required).

List merge request diffs with pagination (merge_request_iid or source_branch required). For one known resource, use the matching get tool.

Get diffs for specific files from a merge request (merge_request_iid or source_branch required).

Update a merge request (merge_request_iid or source_branch required). Use the create tool for new resources and a note tool for comments.

Create a new thread on a merge request. Start a review thread. Use create_merge_request_note for an unthreaded note and create_merge_request_discussion_note to reply.

Resolve a thread on a merge request. Mark an existing review thread resolved. Use update_merge_request_discussion_note to change note text.

List discussion items for a merge request. List complete discussion threads. Use get_merge_request_notes for flat notes.

Get a single discussion item for a merge request. Fetch one discussion by id. Use mr_discussions for a collection and get_merge_request_note for a flat note.

Get a specific note for a merge request. Fetch one note by id. Use get_merge_request_notes for a collection and mr_discussions for threads.

List notes for a merge request. List flat notes. Use mr_discussions when thread structure and resolution state are required.

Add a note to an issue, optionally replying to a discussion thread. Add a note to an existing issue, optionally as a reply. Use update_issue for issue fields.

List issues (default: created by current user; use scope='all' for all). Use this for issue management: list GitLab issues, optionally scoped with project_id. Use get_issue when the iid is known and my_issues for the current user's assignments.

List issues assigned to the authenticated user. Use this for issue management: list issues assigned to the authenticated user. Use list_issues for project-wide listing and get_issue for one issue. Requires classic read_user or fine-grained User:Read.

Get details of a specific issue. Returns the issue with a slim nested milestone by default; set full_response=true for the complete milestone object. Use this for issue management: inspect one issue. Use list_issues or my_issues to discover issues first.

Update an issue. Returns a slim confirmation by default; set full_response=true for the complete updated issue object. Change fields on an existing issue. Use update_issue_description_patch for a targeted description edit and create_issue_note for discussion.

Apply a patch (search/replace or unified diff) to an issue description. Reduces token usage by allowing small changes without sending the full description. Supports dry_run to preview changes and create_note to summarize updates.

List discussions for an issue. List threaded discussions for an issue. Use list_issues or get_issue for issue records.

Get details of a specific project. To find resources, use the matching list or search tool.

List projects accessible by the current user. For one known resource, use the matching get tool.

List members of a GitLab project. Search project members by name or username. Use list_group_members for a group.

List labels for a project. For one known resource, use the matching get tool.

List files and directories in a repository.

List merge requests (without project_id: user's MRs; with project_id: project MRs). For one known resource, use the matching get tool.

Get current authenticated user details. Requires classic read_user or fine-grained User:Read. Use get_user or get_users to look up another user.

List repository commits with filtering options. For one known resource, use the matching get tool.

Get details of a specific commit. To find resources, use the matching list or search tool.

Get changes/diffs of a specific commit. Return the file diffs for one commit. Use get_commit for metadata without the patch.

Get git blame for a file at a given ref. Each entry maps a contiguous range of source lines to the commit that last changed them (id, author, authored_date, message). Use range_start/range_end to limit blame to specific lines.

Verify server status and authentication. Always reports the MCP server version (mcp_server_version). When authenticated, also reports the GitLab instance version from GET /api/v4/version (version, revision, enterprise). Version lookup failures do not fail the health check — those fields are omitted.

Discover and activate additional tool categories for this session. Available categories: core, merge_requests, issues, repositories, branches, projects, labels, ci, groups, pipelines, milestones, wiki, releases, tags, snippets, users, workitems, webhooks, search, variables, dependency_proxy, vulnerabilities, orbit. Already-active categories are listed in the response. Explicit-only toolsets are omitted; list them in GITLAB_TOOLSETS.

Return a short GitLab workflow guide. Omit topic for the overview and topic list. Use this for a short workflow guide (code-review, pipelines, issues, token-saving). Omit topic for the overview. Detailed GitLab operations stay on the typed tools.