Devflow MCP

@cocaxcode/devflow-mcp

Your Jira + GitHub/GitLab workflow, handled by your AI assistant.

One MCP server. 32 tools. Say what you need, it gets done.

Overview · Just Talk to It · Installation · Project Scopes · Tools · Flows · Rules · Storage · Compatibility · Architecture

---

Overview

The most complete MCP server for developer workflow automation. 32 tools that connect Jira (Cloud + Server) with GitHub/GitLab (cloud + self-hosted) — so your AI assistant can manage issues, branches, PRs, and deployments without you ever opening a browser tab.

It auto-detects your Jira version and git provider, enforces configurable safety rules, and lets you define custom YAML flow playbooks for repeatable workflows. Projects are configured once and remembered — each with its own Jira instance, git provider, branch conventions, credentials, and directory scopes. The project that matches your current directory activates automatically (default), or you can switch to another for the session (active). All credentials stay local in `~/.devflow-mcp/` — nothing is synced, nothing is tracked, nothing leaves your machine.

---

Just Talk to It

You don't memorize tool names. You talk naturally and the assistant picks the right tools.

"Set up a project for my Jira + GitHub"

> df_project_setup with:

name: "my-backend" jiraUrl: "https://myteam.atlassian.net" jiraEmail: "dev@myteam.com" jiraToken: "ATATT3x..." jiraProjectKey: "PROJ" gitToken: "ghp_..."

Auto-detects:

• Jira Cloud (API v3)
• GitHub (org/my-backend)
• Base branch: main
• Scope: C:/repos/my-backend (your CWD, auto-added)

"List my projects"

Projects:

my-backend [default] [active] scopes: C:/repos/my-backend my-frontend scopes: C:/repos/my-frontend

"Switch to my-frontend for this session"

Active project switched to: my-frontend (session only)

Default remains: my-backend (based on your current directory)

"Let's work on PROJ-123"

> Reading PROJ-123...

Title: Add OAuth login Status: To Do | Priority: High

Branch feat/PROJ-123 not found. Creating...

branch: feat/PROJ-123-add-oauth-login base: main Confirm? (confirm: true to execute)

Moved PROJ-123 → In Progress

Assigned to you

"Show me my tasks for the ACME project"

ACME-45  Fix OAuth login             In Progress  High

ACME-52 Dashboard refactor To Do Medium ACME-61 Update dependencies To Do Low

"Push my changes"

Preview:

branch: feat/PROJ-123-add-oauth-login pending commits:

• a1b2c3d feat: add login component
• d4e5f6g feat: add auth service

Confirm? (confirm: true to execute)

"Merge main into my current branch"

Conflict detected:

• src/auth/login.ts
• src/config/routes.ts

Resolve the files and commit to complete the merge.

"Create a PR titled 'feat: add OAuth login'"

PR created:

url: https://github.com/org/repo/pull/42 title: feat: add OAuth login provider: github

"Comment on PROJ-123 that the PR is ready for review"

Preview:

issue: PROJ-123 comment: "PR ready for review: https://github.com/org/repo/pull/42"

Confirm? (confirm: true to publish)

"Create a fix branch for PROJ-456 with description fix-oauth-redirect"

Preview:

branch: fix/PROJ-456-fix-oauth-redirect base: main actions: checkout main → pull → create branch

Confirm? (confirm: true to execute)

---

Installation

Claude Code (recommended)

# Global — available across all your projects

claude mcp add --scope user devflow -- npx -y @cocaxcode/devflow-mcp@latest

Per-project

claude mcp add devflow -- npx -y @cocaxcode/devflow-mcp@latest

Claude Desktop

macOS: ~/Library/Application Support/Claude/claude_desktop_config.json

{

"mcpServers": { "devflow": { "command": "npx", "args": ["-y", "@cocaxcode/devflow-mcp@latest"] } } }

</details>

Windows: %APPDATA%\Claude\claude_desktop_config.json

{

"mcpServers": { "devflow": { "command": "npx", "args": ["-y", "@cocaxcode/devflow-mcp@latest"] } } }

</details>

Cursor / Windsurf

// .cursor/mcp.json or .windsurf/mcp.json

{ "mcpServers": { "devflow": { "command": "npx", "args": ["-y", "@cocaxcode/devflow-mcp@latest"] } } }

VS Code / Codex / Gemini CLI

{

"mcpServers": { "devflow": { "command": "npx", "args": ["-y", "@cocaxcode/devflow-mcp@latest"] } } }

---

Project Scopes

Each project has paths (scopes) — the directories that belong to it. A directory can only be the scope of one project.

This gives you two concepts:

• Default project: The project whose scope matches your current working directory. This is automatic and persistent — if you are inside C:/repos/my-backend and that directory is a scope of my-backend, then my-backend is the default. No action needed.

• Active project: The project you are currently working with. By default it equals the default project, but you can switch it manually with df_project_switch for the current session. This resets to the default when you restart.

df_project_list shows both the default and active indicators so you always know where you stand.

Practical example

"Set up a project called my-backend"

→ CWD (C:/repos/my-backend) is auto-added as scope

"Set up another called my-frontend" → Run from C:/repos/my-frontend, that directory becomes its scope

"List projects" → my-backend [default] [active] scopes: C:/repos/my-backend my-frontend scopes: C:/repos/my-frontend

"Switch to my-frontend" → Session switches. Now my-frontend is active for checking issues, etc.

"List projects" → my-backend [default] scopes: C:/repos/my-backend my-frontend [active] scopes: C:/repos/my-frontend

Close and reopen → my-backend is active again (matches CWD = default)

This means you can work across multiple projects with different Jira instances and git providers — the right credentials are always selected based on where you are, and you can always override for the session when needed.

---

Tools

32 tools organized in 5 categories.

Projects (5)

Example: setting up a project

df_project_setup with:

name: "my-project" jiraUrl: "https://myteam.atlassian.net" jiraEmail: "dev@myteam.com" jiraToken: "ATATT3x..." jiraProjectKey: "PROJ" gitToken: "ghp_..."

Auto-detects:

• Jira Cloud (API v3)
• GitHub (org/my-project)
• Base branch: main
• Scope: your CWD (auto-added)

</details>

Jira (6)

Git (7)

Important: df_branch, df_checkout, and df_push verify the working directory before executing. They block if there are uncommitted files or unpushed commits, listing exactly what needs attention. This prevents accidental work loss.

Flows (5)

Rules (9)

---

Flows

Flows are YAML playbooks that define step sequences. They don't run automatically -- you tell the assistant when to use them.

Default: start-task

Triggered when you say something like _"let's work on PROJ-123"_:

name: start-task

trigger: "when the user says 'let's work on', 'start task', 'new task' + issue ID" steps:

• tool: df_issue note: "Read issue detail and summarize the task"
• tool: df_find_branch note: "Check if a branch already exists for this issue"
• tool: df_branch confirm: true note: "Only if no existing branch was found"
• tool: df_statuses note: "Get transitions to find the 'In Progress' transition ID"
• tool: df_transition target: "In Progress" confirm: true
• tool: df_assign note: "Assign the issue if it has no assignee"

Custom flows

Create your own by asking naturally:

_"Create a flow called 'finish-task' that pushes, creates a PR, and comments on Jira"_

name: finish-task

trigger: "when the user says 'finish task', 'wrap up' + issue ID" steps:

• tool: df_push confirm: true note: "Push pending commits"
• tool: df_pr note: "Create PR/MR to base branch"
• tool: df_comment confirm: true note: "Comment on the issue with the PR link"

The start-task flow can be modified but not deleted. Use df_flow_update to change any flow's steps, trigger, or name.