MCP Tools

Sciak Flow exposes a set of Model Context Protocol (MCP) tools, so AI assistants running inside IntelliJ (such as Claude Code or GitHub Copilot Chat) can interact with GitLab pipelines, merge requests, and issues without leaving the IDE.

Every tool takes a currentDirectory parameter — the absolute path of the working directory inside the repository — which is used to identify which open IntelliJ project the call applies to.

Pipeline Tools

getLastPipeline: Retrieves the most recent pipeline for a given branch name from the currently fetched pipeline window. Returns pipeline metadata including run status, commit SHA, web URL, and timestamps. Returns null if no pipeline for that branch appears in the fetched results — this does not necessarily mean no pipeline has ever run on that branch.
getPipelineJobs: Returns all jobs for a given pipeline ID, including job name, stage, status, duration, and web URL. Includes retried jobs.
getPipelineJobLog: Fetches the plain-text log of a pipeline job by its numeric job ID. ANSI escape sequences are stripped from the output.

Merge Request Tools

getMergeRequest: Fetches a merge request by its numeric IID (the per-project number shown in the merge request URL/UI — not the global database id). Returns metadata including title, state, source/target branches, web URL, and CI pipeline status. Returns null if no merge request exists with that IID.
getMergeRequestDiffs: Returns all file diffs for a merge request, identified by its numeric IID. Each diff entry includes old/new file paths, change-type flags (new, renamed, deleted), and unified diff content. Returns an empty list if no merge request exists with that IID.
createMergeRequest: Creates a new merge request from a given source branch. If targetBranch is not specified, the project's configured default branch is used. The sourceBranch must match the branch currently checked out in the working directory, which must have no uncommitted changes and must be pushed to the remote (in sync with its tracked remote branch). Returns the created merge request's metadata, including its IID and web URL.
addMergeRequestComment: Adds a general comment to a merge request, identified by its numeric IID. The comment is a top-level merge request note — not attached to any specific diff line. Returns the created note's metadata.
addMergeRequestLineComment: Adds a comment attached to a specific line of a file in a merge request's diff, identified by the merge request's numeric IID. Exactly one of newLine or oldLine must be provided: newLine for a line added/unchanged in the new version of the file (requires newPath), oldLine for a line removed/unchanged in the old version of the file (requires oldPath). Returns the created note's metadata, including its discussion id.

Issue Tools

getIssue: Fetches an issue by its numeric IID (the per-project number shown in the issue URL/UI — not the global database id). Returns metadata including title, description, state, labels, and web URL.
createIssue: Creates a new issue with the given title and description. Any issue template configured on the project is ignored — the description is used verbatim. Labels, assignees, and milestones are not set as structured fields; include them as free text in the description if needed. Returns the created issue's metadata, including its IID and web URL.

18 July 2026