Get the authenticated user. Call this first: it is the cheapest way to prove the token and base URL work before any write.

Get the GitLab version answering this token (GET /version). Confirms which version the instance is on, which matters because most public documentation describes newer releases.

Call any API v4 endpoint directly - the escape hatch for endpoints with no dedicated tool (issues, labels, pipelines, snippets, members). Prefer a dedicated tool when one exists: this one does no validation, so a wrong path or field is exactly what the instance receives.

Get a project by id or path. Use it to turn a project name into the path the other tools take, and to read default_branch.

Search projects visible to this token by name. Use it when the exact project path is unknown.

List a project's labels. Check here before setting labels: 11.3 creates an unknown label silently when the account may, and rejects it when the account may not.

Find users by name or username. Needed because 11.3 assigns and filters by numeric user id and never by username.

List a project's branches. Useful before gitlab_mr_create to confirm the source branch exists and to find the target branch.

Read one file from the repository at a ref. Defaults to the project default branch - pass ref= to read the file as the merge request sees it. Output is capped, and a truncated read says so.

List a project's merge requests. Defaults to state=opened because the raw API would return every state at once. This version has no reviewers or draft filter - read work_in_progress on each item instead.

Get one merge request. Read state before anything else: only an opened merge request can be merged, and a merged one still reports merge_status can_be_merged. work_in_progress says whether it is a draft.

The merge request diff, summarised per file: status, added/removed line counts and a capped patch. Read this before commenting on a line, and to learn which paths and lines exist. Use path to pull one file's patch at a larger cap.

Create a merge request from source_branch into target_branch. On 11.3 there is no reviewers attribute (assign instead) and no draft parameter: pass draft:true and the required "WIP: " title prefix is applied for you. Creating an MR whose branches already have an open one fails with 409 - update that one instead.

Update a merge request. Pass draft to set or clear the "WIP: " prefix (when no title is given the current title is read first). labels:[] clears all labels and assignee_id:0 unassigns - omitting a field leaves it alone.

Post a comment on the merge request itself. For a comment on a specific line of the diff, use gitlab_mr_comment_on_line so it appears in the changed line's thread.

Merge a merge request. The merge request must be opened - merging a merged or closed one fails. It fails with 405 while it is not mergeable (conflicts, or a required pipeline still running) and with 409 when the source branch moved since you read it, so read the merge request first and pass its sha to pin the merge.

List the pipelines recorded against this merge request. Read before merging: 11.3 refuses the merge while one is running or failed.

List the diff versions of a merge request, newest first as GitLab returns them. Only needed to debug comment positions - gitlab_mr_comment_on_line resolves them itself.

List the discussion threads of a merge request, with each diff comment's file and line. System notes are filtered out by default and resolved is derived from the thread's notes, so the returned page can be shorter than pagination.total (which is GitLab's raw count).

Comment on one line of the merge request diff, as a normal review comment. Give the path exactly as gitlab_mr_changes reports it and the line number in that side of the file. The required base/start/head SHAs and the old-side line number are resolved from the merge request's latest diff version, so a stale SHA or a line that is not in the diff is reported instead of being sent. The result carries discussion_id - pass it to gitlab_mr_reply to continue the thread.

Reply inside an existing discussion thread. Use it to answer a review comment instead of starting a second thread on the same line.

Resolve or unresolve a discussion thread. This is how review state is recorded on CE 11.3, which has no approve API. Reply to the thread first if the resolution needs an explanation.

List a project's issues. Read-only extra: this file declares the endpoints the merge-request tools do not cover, so they cost no code.

Get one issue by its project-scoped iid.

List a project's members with their access level and numeric user id - the ids gitlab_mr_create/update take as assignee_id.

List a project's pipelines, optionally filtered by ref or status. On 11.3 a merge request's own pipelines come from gitlab_mr_pipelines.

List the jobs of a pipeline with their status, stage and failure reason. Job logs are text, not JSON, so they are not reachable from this JSON layer.

List repository commits on a ref. Use it to see what a merge request's source branch contains beyond the diff.

List repository tags.

List the projects of a group (including its subgroups), to find a project path from a group.