DEVELOPER TOOLS

MCP server

Updated October 24, 2026 · 9 min read
The DevFlow MCP server gives your AI coding agent one tool per DevFlow action — 24 in all, plus list_actions and resolve_context. Tools work out the project, issue and repository from the folder the agent runs in.
An AI coding agent calling DevFlow MCP tools

01Add it to your agent

Needs Node.js 20 or newer, DevFlow Desktop in the tray and Chrome open with the DevFlow extension. Restart the agent after editing its config, then check that the devflow tools are listed.
Run in your terminal
$ claude mcp add devflow -- npx -y @devflow-one/mcp
The Cursor entry also works in Claude Desktop’s claude_desktop_config.json and in a project’s .mcp.json.

02Routing fields

Every action tool takes these fields. All are optional — left out, they’re worked out from the agent’s folder like the CLI does: git remote, checkout folder, branch name, then folder name.
FIELDWHAT IT DOESTYPE
issueIdJira issue, e.g. ABC-123. Its prefix picks the project. Found from the branch or folder when left out.string
projectKeyJira project key. Wins over the git remote and folder.string
profileChrome profile to send the action to, when several are connected.string
repoRepository id or URL. Only needed when the project has several and none can be found from the folder.string
allowDestructiveOnly on destructive tools. Must be true or the call is refused. Never filled in for you.boolean
The DEVFLOW_PROJECT, DEVFLOW_ISSUE, DEVFLOW_REPO and DEVFLOW_PROFILE environment variables in the server’s config work as defaults. DevFlow never guesses: if two projects match, the call fails until you pass projectKey or repo.

03Start here

Two tools help the agent find its bearings before it acts.
List actions
list_actions
Lists the actions DevFlow Desktop offers and the connected Chrome profiles with the projects each one owns. Action names are the internal ones, e.g. createBranch, not tool names.
Resolve context
resolve_context
Shows what a folder resolves to: project, issue, repository, base branch and profile, whether that profile is connected, how each was found, close matches and warnings. Read-only. Git runs only when the folder is a configured repository or a DevFlow-managed copy. The issue it returns isn’t the branch to work on — use resolve_branch_name for that.
NAMETYPEREQUIREDDESCRIPTION
cwdstring—Folder to check. Defaults to the folder the server runs in.
issueIdstring—Same as the routing field.
projectKeystring—Same as the routing field.
profilestring—Same as the routing field.
repostring—Same as the routing field.

04Issues

Read-only, and default to the issue found from your branch or folder. Issue status needs the Jira API token set in Settings.
Get issue status
get_issue_status
Returns the issue’s Jira status and its parent’s, as the panel’s status bar shows them. Needs the Jira API token set in Settings. Read-only.
NAMETYPEREQUIREDDESCRIPTION
issueIdstring—Issue to look up. Defaults to the issue found from your folder.
List issue branches
list_issue_branches
Lists each repository’s remote branches for the issue, and for its parent when the repo card includes it. Read-only.
NAMETYPEREQUIREDDESCRIPTION
issueIdstring—Issue to look up. Defaults to the issue found from your folder.
List issue pull requests
list_issue_pull_requests
Lists each repository’s pull requests for the issue in every state, merged and closed included, with approvers on open ones — the same list the repo card shows. Read-only.
NAMETYPEREQUIREDDESCRIPTION
issueIdstring—Issue to look up. Defaults to the issue found from your folder.

05Branches

Every tool on this page also takes the routing fields. The repository’s branch template always decides the branch name.
Create branch
create_branch
Creates the issue’s branch, or reuses it if it already exists. The template decides the name, so a sub-task may share its parent’s branch; a replaced branchName is listed in warnings. Needs issueId or branchName. If it times out, check whether the branch exists before you retry.
NAMETYPEREQUIREDDESCRIPTION
branchNamestring—Fallback name, used only when the template can’t be applied. Its issue key is used when issueId is left out.
issueIdstring—Its own field here: the issue whose branch to create. When both it and branchName are left out, the issue found from the folder is used.
fromBranchstring—Existing remote branch to start from. Defaults to the repository’s base branch.
Resolve branch name
resolve_branch_name
Returns the branch an issue’s work belongs on and whether it exists yet. Call it before create_branch, commit_by_template or create_draft_pull_request. Read-only.
NAMETYPEREQUIREDDESCRIPTION
issueIdstringIssue to look up, e.g. ABC-123.
Delete branch
delete_branch
Deletes a branch in the project’s repository. Destructive. If it times out, check the branch before you retry.
NAMETYPEREQUIREDDESCRIPTION
branchNamestringBranch to delete.
allowDestructivebooleanMust be true.

06Commits

The default commit template is the summary, then the list of changes, then the issue slug.
Commit by template
commit_by_template
Commits a folder with the project’s commit template, then pushes to origin. In a DevFlow-managed copy it stages every changed or deleted tracked file; in your own checkout it commits only what is already staged. It commits whichever branch is checked out and won’t push from the base branch. Pushing is destructive. Returns the commit SHA, whether it pushed and the staged files. If it times out, it may already have committed or pushed.
NAMETYPEREQUIREDDESCRIPTION
worktreePathstringFolder to commit: a DevFlow-managed copy or the repository’s local path from Settings. Any other folder is refused.
valuesobject—Values for the template: summary (the subject line), changesList (a list of strings, written as bullets), issueSlug and prNumber. Custom templates can use other keys. Empty values still commit and are listed in warnings.
pushboolean—Defaults to true. false commits locally and isn’t destructive.
includeUntrackedboolean—Also stages new files that aren’t ignored. Defaults to false.
allowDestructiveboolean—Must be true unless push is false.

07Pull requests

Merge requests on GitLab. Tools that take a pull request use its number in prId.
Create draft pull request
create_draft_pull_request
Opens a pull request from the issue’s branch, always as a draft. The PR type fills the title, description and labels from its templates; if a template can’t be filled, the given title and body are used and the reason is listed in warnings. If it times out, call find_pr_by_issue_key before you retry — the pull request may already exist.
NAMETYPEREQUIREDDESCRIPTION
titlestringPull request title.
bodystringFallback description, used when the PR type template (which uploads media via its own {prMedia}) can’t be filled; {prMedia} here is filled or removed. Required here, unlike the CLI’s --body.
headBranchstring—Source branch. A branch that exists on the remote is used as is; otherwise the issue’s branch from the template is used.
baseBranchstring—Target branch. Defaults to the repository’s base branch; a pattern like {year}/{number} picks the newest matching branch.
prTypestring—PR type id or label. Picked from the title prefix, branch prefix, Jira issue type or title words, else the first type. Call list_pr_types first.
issueIdstring—The routing field, also used to tie the pull request to the issue for the templates. Filled in from the folder when both it and headBranch are left out.
Mark ready for review
mark_pr_ready_for_review
Takes a draft pull request out of draft. Also applies the PR type's labels, assigns you if no one is assigned and asks the type's missing reviewers. To refresh these later, call mark_pr_as_draft and then this again.
NAMETYPEREQUIREDDESCRIPTION
prIdintegerPull request number.
prTypestring—PR type id or label to switch to, swapping its labels. See list_pr_types.
Mark as draft
mark_pr_as_draft
Turns a pull request back into a draft.
NAMETYPEREQUIREDDESCRIPTION
prIdintegerPull request number.
Close pull request
close_pull_request
Closes a pull request without merging. Destructive. If it times out, check the pull request before you retry.
NAMETYPEREQUIREDDESCRIPTION
prIdintegerPull request number.
allowDestructivebooleanMust be true.
Merge pull request
merge_pull_request
Merges a pull request. If the provider says no — conflicts, missing approvals, a protected branch — it fails with the provider’s reason. Destructive. If it times out, check the pull request before you retry.
NAMETYPEREQUIREDDESCRIPTION
prIdintegerPull request number.
mergeMethodenum—merge, squash or rebase. Defaults to the provider’s setting.
deleteSourceBranchboolean—Deletes the source branch after the merge.
allowDestructivebooleanMust be true.
Assign
assign_pr
Assigns a pull request to a user.
NAMETYPEREQUIREDDESCRIPTION
prIdintegerPull request number.
assigneestringUsername to assign.
Find by issue
find_pr_by_issue_key
Finds the pull request for an issue. Read-only.
NAMETYPEREQUIREDDESCRIPTION
issueKeystringIssue to search by. Separate from the routing issueId.
Get pull request
get_pull_request
Reads a pull request’s title, description, link, state, draft flag, and source and target branch. Read-only.
NAMETYPEREQUIREDDESCRIPTION
prIdintegerPull request number.
Update pull request
update_pull_request
Changes the title, description or target branch, then returns the pull request as saved. Pass at least one change. description and appendDescription can’t be used together. To refresh videos and screenshots, swap the old media links for {prMedia}: DevFlow uploads .devflow/media/<ISSUE-KEY>[-n].{mp4,png,jpg,jpeg}, puts the new links there and lists them in the result’s media. If the upload fails or the branch names no issue, {prMedia} is removed and media.error says why.
NAMETYPEREQUIREDDESCRIPTION
prIdintegerPull request number.
titlestring—New title.
descriptionstring—Replaces the whole description, exactly as given.
appendDescriptionstring—Adds text after a --- line. Skipped if the description already ends with it, so calling it twice is safe.
baseBranchstring—New target branch. It must exist on the remote.
List PR types
list_pr_types
Lists the repository’s PR types with their id, label and which one is the default. Empty if none are set up. Read-only.
Get fix-comments prompt
get_fix_comments_prompt
Returns the prompt DevFlow uses to fix review comments: the base prompt plus your project’s fix rules. It runs no AI and changes nothing.
NAMETYPEREQUIREDDESCRIPTION
prIdinteger—Pull request the prompt is for.
issueKeystring—Issue the prompt is for.
Get review comment counts
get_pr_review_comment_counts
Counts a pull request’s review comments as the Fix Comments row does: unfixed, fixed, resolved and prComments. Read-only.
NAMETYPEREQUIREDDESCRIPTION
prIdintegerPull request number.
Fix comments
fix_pr_comments
Starts an AI fix of the pull request’s review comments in the repository’s local folder, like Fix Comments in the panel. The run commits and pushes, so it’s destructive and needs allowDestructive: true. It returns at once with started, prNumber and queued, which is true when an automation run is busy and the fix starts on its next tick. It returns started: false with a reason while the panel or the timer is already fixing that pull request. Call get_pr_review_comment_counts later to see the counts change.
NAMETYPEREQUIREDDESCRIPTION
prIdintegerOpen pull request to fix.
allowDestructivebooleanMust be true, or the call is refused.
Reply as fixed
reply_pr_comments_fixed
Replies “Fixed” to every unanswered review thread, like Reply as Fixed in the panel, and resolves each one when the repository is set to. Returns success, failed and resolved counts. If it times out, check the counts before you retry.
NAMETYPEREQUIREDDESCRIPTION
prIdintegerPull request number.

08Pipelines

Pipelines on GitLab, workflow runs on GitHub.
Pipeline status
get_pipeline_status
Gets the pipeline status for a pull request’s latest commit. Read-only.
NAMETYPEREQUIREDDESCRIPTION
refobjectThe pull request and its latest commit: prId (integer) and headSha (string), both required.
List pipeline jobs
list_pipeline_jobs
Lists the pipeline jobs for a pull request’s latest commit. Read-only.
NAMETYPEREQUIREDDESCRIPTION
refobjectThe pull request and its latest commit: prId (integer) and headSha (string), both required.
Restart one job
restart_pipeline_job
Restarts a single job. If it times out, check the job before you retry.
NAMETYPEREQUIREDDESCRIPTION
jobIdintegerId of the job to restart.
Restart failed jobs
restart_failed_jobs
Restarts only the failed jobs of a pipeline or run. If it times out, check the pipeline before you retry.
NAMETYPEREQUIREDDESCRIPTION
pipelineOrRunIdintegerPipeline id on GitLab, run id on GitHub.
Restart all jobs
restart_all_jobs
Restarts every job of a pipeline or run. If it times out, check the pipeline before you retry.
NAMETYPEREQUIREDDESCRIPTION
pipelineOrRunIdintegerPipeline id on GitLab, run id on GitHub.

09Slack

Messages are posted from your own Slack account.
Notify Slack
notify_slack
Sends a message to the project’s Slack channels that get messages automatically, or to one you name. Fails if Slack isn’t set up for the project. If it times out, check the channel before you retry, or the message may be posted twice.
NAMETYPEREQUIREDDESCRIPTION
messagestringThe message. Can include {key} placeholders and @name mentions.
channelstring—Channel id to send to instead.
valuesobject—Values for the placeholders, as text.
prNumberinteger—Pull request whose reviewers this notifies. The post is saved for get_reviewer_notify_status, and a channel already notified for it gets a ping in the earlier message’s thread.
Get reviewer notify status
get_reviewer_notify_status
For each reviewer channel the panel’s Notify button shows, says whether reviewers were already notified, with the message link, and the nextAction: send or ping. Its source says who posted: manual (panel), auto (auto-send), gateway (notify_slack) or slack (found only in Slack history). Either way, follow up with notify_slack and prNumber. Read-only.
NAMETYPEREQUIREDDESCRIPTION
prIdintegerPull request number.
List Slack channels
list_slack_channels
Lists the project’s Slack channels: id, name, label, which PR labels they’re for, and whether notify_slack sends to them automatically. Returns no templates or tokens. Read-only.

10Destructive tools

These tools are refused unless the call sets allowDestructive to true. It’s never filled in for you, and DevFlow Desktop checks it again.
TOOLWHEN IT NEEDS CONFIRMINGFIELD
delete_branchAlways.allowDestructive: true
close_pull_requestAlways.allowDestructive: true
merge_pull_requestAlways.allowDestructive: true
commit_by_templateWhen it pushes, which is the default. Not with push set to false.allowDestructive: true
fix_pr_commentsAlways. Its AI run commits and pushes.allowDestructive: true
Without it the call fails with DESTRUCTIVE_BLOCKED before anything runs.

11Errors

A failed call comes back marked as an error, with the code, message and any hint in the result. Missing or wrong-typed fields are rejected before the tool runs.
CODEWHAT IT MEANSWHAT TO DO
NO_CONTEXTNo project or issue could be found.Pass issueId or projectKey
AMBIGUOUS_PROFILESeveral profiles or repositories match; the error lists them.Pass projectKey, repo or profile
NO_PROFILEThe Chrome profile that owns the project isn’t connected.Open that profile in Chrome
DESTRUCTIVE_BLOCKEDA destructive tool was called without allowDestructive.Set allowDestructive: true
TIMEOUTNo result in time. delivered says whether DevFlow picked the action up — if it did, it may still finish.Follow the hint before retrying
GATEWAY_UNREACHABLEDevFlow Desktop isn’t running.Start DevFlow Desktop
INVALID_PAYLOADBad inputs, e.g. update_pull_request with nothing to change.Fix the inputs
HANDLER_FAILEDThe extension or your Git provider refused; the message has the reason.Read the message

12Good to know

Twelve tools aren’t safe to retry blindly
create_branch, delete_branch, commit_by_template, create_draft_pull_request, close_pull_request, merge_pull_request, fix_pr_comments, reply_pr_comments_fixed, the three restart tools and notify_slack. If one times out after DevFlow picked it up, the error has a hint — check before calling it again.
Some tools wait longer
Most tools wait up to 30 seconds. commit_by_template, get_fix_comments_prompt, list_issue_pull_requests and reply_pr_comments_fixed wait up to 2 minutes, and create_draft_pull_request and update_pull_request just under 5.
Warnings come with the result
Things like a replaced branch name or an empty template value are listed in the result’s warnings, so the agent can tell you about them.