Log inSubmit server
Devflow MCP logo

Devflow MCP

Connects Jira with GitHub or GitLab to manage issues, branches, merges, pull requests, projects, flows, and rules.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Devflow MCP

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "devflow-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@cocaxcode/devflow-mcp@latest"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Automated check passed— started and listed 32 tools correctly (13d ago).

Overview

The devflow-mcp MCP server connects Jira Cloud or Server with GitHub or GitLab for issue and Git workflow operations. It exposes tools for project selection, assigned issues, status transitions, branches, pushes, merges, and pull or merge requests. Projects can be matched to working-directory scopes, with credentials stored locally under ~/.devflow-mcp/. Reach for it when an MCP client needs to coordinate Jira work with repository changes across multiple projects.

Use cases

  • Configure Jira and Git credentials for a repository
  • List assigned Jira issues for the active project
  • Create and switch to an issue branch
  • Push changes and open a pull or merge request
  • Define reusable flows and project-specific rules

Key features

  • Jira Cloud and Server support
  • GitHub and GitLab branch operations
  • Directory-scoped project selection
  • Issue transitions, assignment, and comments
  • GitHub pull request and GitLab merge request creation
  • Custom flows and configurable rules

Tools32

What Devflow MCP lets your agent do. Expand a tool for its parameters.

Verified live~3.4k tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 1d ago

Recent health check succeeded.

8/8 checks healthy over the last 42d

What it can do

From the 32 tools this server returned when we ran it.

Can delete or modify data · 4Handles credentials · 1Makes network requests · 2Read-only tools · 28
Network at startup3 connections
Files written at startupNone
Install scriptsprepare
npm provenanceNot published
Package age215 days
Maintainers1

Observed 2026-10-22 in an isolated sandbox. A description of reach, not a security audit.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 12d ago via OSV.dev · @cocaxcode/devflow-mcp@latest (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars1Stargazers on the source repository.
npm downloads253Package downloads in the last 30 days.
Last commit7mo agoMost recent push to the default branch.
Availability100%Our rolling endpoint + install checks that succeeded.
Install checkPassedOur sandbox started it and listed its tools.
Tools exposed32Callable tools this server registers over MCP.
Directory activity3 viewsConfig copies, upvotes, and views on AllMCPs.

How Devflow MCP works

What devflow-mcp MCP server does

The devflow-mcp MCP server coordinates Jira work with Git operations through one MCP interface. It supports Jira Cloud and Server, plus GitHub and GitLab, including cloud and self-hosted Git providers according to the project configuration. The tool set covers project configuration, issue inspection and updates, branch management, remote synchronization, pull or merge request creation, and workflow customization.

A configured project holds its Jira instance, Git provider, branch conventions, credentials, and directory scopes. The current working directory can select a default project automatically. An active project can also be selected for the current session, which is useful when several repositories or Jira projects are configured.

How it works

Start by configuring a project with df_project_setup. The server can detect the Jira version and Git provider from the supplied configuration, and it adds the current directory as a scope. df_project_list reports which project is default and which is active. df_project_switch changes the active project for the session; restarting returns selection to the directory-based default.

Issue tools list assigned work, retrieve issue details, show available transitions, move issues between statuses, assign issues to the current user, and add comments. Git tools can create feat/ or fix/ branches from a base branch, find branches by issue key, check out branches, pull, push, and merge. df_pr creates a GitHub pull request or GitLab merge request.

Many mutating actions use a confirmation step. The examples show previews before operations such as branch creation, pushing, commenting, or transitions are executed. Checkout includes a safety guard, and merge operations can report conflicts that must be resolved before completion.

Setup and configuration

Install the package through an MCP client using npx -y @cocaxcode/devflow-mcp@latest. The README provides stdio configurations for Claude Code, Claude Desktop, Cursor, Windsurf, VS Code, Codex, and Gemini CLI. Claude Code supports both user-wide and per-project registration.

Project credentials are supplied during project setup rather than through documented environment variables. Use project update and delete tools to maintain existing configurations.

Tools and capabilities

The devflow-mcp MCP server groups its 32 tools into these practical areas:

  • Project lifecycle: create, update, list, switch, and delete projects.
  • Jira work: list assigned issues, inspect details, view statuses, transition issues, assign them, and comment.
  • Git operations: create and locate branches, check out, pull, push, and merge.
  • Review creation: open GitHub pull requests or GitLab merge requests.
  • Custom automation: create, list, inspect, update, and delete flows; manage global rules and project-specific rule overrides.

Custom flows provide reusable playbooks, while rules can be enabled or disabled globally and overridden for individual projects. The start-task flow is protected from deletion.

Limitations and notes

The material documents stdio installation and does not describe a network transport. It also does not list environment variables for configuration. Git and Jira actions depend on valid project credentials and provider configuration. Project scopes cannot overlap: a directory belongs to only one project. Session-level project selection resets when the server is restarted, and directory matching determines the default project again.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Devflow MCP

devflow-mcp is an MCP server that connects Jira Cloud or Server with GitHub or GitLab. Its main tools manage projects, assigned issues, issue transitions, branches, pulls, pushes, merges, pull or merge requests, custom flows, and workflow rules from an MCP-compatible client.

Install it with npx using `npx -y @cocaxcode/devflow-mcp@latest` in an MCP client configuration. The README includes setup examples for Claude Code, Claude Desktop, Cursor, Windsurf, VS Code, Codex, and Gemini CLI.

Yes, devflow-mcp works with Cursor through a `.cursor/mcp.json` stdio configuration. Register the server with the package command `npx -y @cocaxcode/devflow-mcp@latest`, then configure a project with the Jira and Git details required by your repositories.

Yes, the server supports Jira Server and GitLab, including self-hosted Git providers according to the project configuration. Use project setup to provide the Jira and Git credentials, project key, provider details, and repository scope.

It uses the current working directory to select a matching default project, based on configured scopes. You can use `df_project_switch` to select another project for the current session, but the selection returns to the directory-based default after restart.

Related MCP servers

All in Developer Tools All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewDevflow MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/devflow-mcp?style=directory)](https://allmcps.com/mcp/devflow-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/devflow-mcp"><img src="https://allmcps.com/api/badge/devflow-mcp?style=directory" alt="Devflow MCP on AllMCPs" /></a>