# devflow-mcp [Health: Active]

**Category:** 💻 Developer Tools  
**Repository:** https://github.com/cocaxcode/devflow-mcp  
**GitHub Stars:** 1  
**npm Downloads (last month):** 253  
**Views:** 3  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/devflow-mcp

## Description
MCP server connecting Jira (Cloud + Server) with GitHub/GitLab. Branches, issues, PRs, flows.

## Tools
Capabilities this server exposes over MCP:

- **df_project_setup** — Configurar un nuevo proyecto: vincula Jira + Git provider. Auto-detecta tipo de Jira, version API, provider Git y rama base. IMPORTANTE: Pide al usuario TODOS los datos de credenciales (email, token, URL). NUNCA inventes ni asumas credenciales.
- **df_project_update** — Modificar la configuracion de un proyecto existente.
- **df_project_list** — Listar todos los proyectos configurados.
- **df_project_switch** — Cambiar el proyecto activo (de sesion). Al reiniciar vuelve al default por scope.
- **df_project_delete** — Eliminar un proyecto configurado.
- **df_issues** — Listar mis issues asignados en Jira. Soporta filtros opcionales por proyecto y estado.
- **df_issue** — Obtener el detalle completo de un issue de Jira. Solo lectura, sin efectos secundarios.
- **df_statuses** — Listar las transiciones disponibles para un issue (los estados a los que se puede mover desde su estado actual).
- **df_transition** — Mover un issue a un nuevo estado. Requiere confirm: true para ejecutar. Sin confirm devuelve preview.
- **df_assign** — Asignar un issue al usuario actual. Si el issue ya tiene asignado, no hace nada.
- **df_comment** — Añadir un comentario a un issue de Jira. Requiere confirm: true para ejecutar.
- **df_branch** — Crear una nueva branch desde la rama base con formato feat/PROJ-123-desc o fix/PROJ-123-desc. Requiere confirm: true. Verifica que no haya cambios sin pushear.
- **df_find_branch** — Buscar si existe una rama local o remota que contenga un issue key (ej: PROJ-123). Devuelve la rama si existe o null.
- **df_checkout** — Cambiar a una rama existente. Verifica que no haya cambios sin pushear antes.
- **df_pull** — Hacer pull de la rama actual desde el remote.
- **df_merge** — Mergear una rama en la rama actual. Requiere confirm: true. Si hay conflictos, los reporta sin abortar.
- **df_push** — Hacer push de la rama actual al remote. Requiere confirm: true para ejecutar. Sin confirm devuelve preview.
- **df_pr** — Crear un Pull Request (GitHub) o Merge Request (GitLab) para la rama actual.
- **df_flow_create** — Crear un nuevo flow (playbook) con nombre, disparador y pasos. El AI lo ejecuta cuando el usuario dice algo que matchea el trigger.
- **df_flow_list** — Listar todos los flows configurados con nombre, disparador y numero de pasos.
- **df_flow_get** — Ver el detalle completo de un flow (nombre, disparador y todos los pasos).
- **df_flow_update** — Modificar un flow existente: cambiar disparador y/o pasos.
- **df_flow_delete** — Eliminar un flow. El flow "start-task" requiere confirm: true.
- **df_rule_create** — Crear una regla configurable. Las reglas pueden bloquear o advertir sobre acciones.
- **df_rule_list** — Listar todas las reglas configuradas con su estado (activada/desactivada).
- **df_rule_get** — Ver el detalle completo de una regla.
- **df_rule_update** — Modificar una regla existente.
- **df_rule_toggle** — Activar o desactivar una regla.
- **df_rule_delete** — Eliminar una regla.
- **df_rule_project_override** — Activar o desactivar una regla global para el proyecto actual. El override solo aplica a este proyecto.
- **df_rule_project_add** — Añadir una regla propia que solo aplica al proyecto actual.
- **df_rule_project_remove** — Eliminar una regla propia del proyecto actual o quitar un override de regla global.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

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

## Documentation

## 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.

_Full upstream README: https://allmcps.com/mcp/devflow-mcp/readme_