io.github.cocaxcode/devflow-mcp

NPM · @COCAXCODE/DEVFLOW-MCP · SCANNED AUG 4

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

Available components

+23 this week 69 69 Trust /100

Trust breakdown (6 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score →

Supply Chain Security87

No malware found by supply-chain analysis.Pass
Only part of the dependency tree could be resolved (96 of 100), so this covers what we could see, not the whole tree.Partial
No install/post-install scripts declared.Pass
Only part of the dependency tree could be resolved (96 of 100), so this covers what we could see, not the whole tree. View diagnostics → Partial

Provenance & Transparency45

Source repository is publicly reachable at the declared URL. View diagnostics → Pass
Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
Clear OSI-approved license (MIT).Pass
Actively maintained (last published 127 days ago).Pass
Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail

Schema Quality & AI Usability71

AI-judged instruction clarity (good).Pass
Tool/resource definitions use about 2100 tokens (~65/item across 32 items; 32 tools + 0 resources), lean.Pass
Usage-examples check failed: none of the tools include examples. See how to fix → Fail

Stability & Change Management30

Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial

Tool Coverage100

100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
100% of tool parameters carry a description.Pass

Capabilities100

Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

npm · @cocaxcode/devflow-mcp

Claude Codex opencode OpenClaw Hermes Other

# add to Claude Code

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

# add to Codex CLI

codex mcp add cocaxcode-devflow-mcp -- npx -y @cocaxcode/devflow-mcp

// opencode.json

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "cocaxcode-devflow-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@cocaxcode/devflow-mcp"
      ],
      "enabled": true
    }
  }
}

# add to OpenClaw

openclaw mcp add cocaxcode-devflow-mcp --command npx --arg -y --arg @cocaxcode/devflow-mcp

# ~/.hermes/config.yaml

mcp_servers:
  cocaxcode-devflow-mcp:
    command: "npx"
    args: ["-y", "@cocaxcode/devflow-mcp"]

// mcp.json

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

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

4 Aug 26 +1

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
2 Aug 26 +32
- Provenance: unverified → fail ▼ security
- Install scripts: unverified → pass ▲ security
- Known CVEs: unverified → partial ▲ security
- Tool coverage: 100 → unverified ▼ functional
- License: unverified → pass ▲ functional
- Dependency health: unverified → partial ▲ functional
- Maintenance: unverified → pass ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Stability: unverified → 0.23 ▲ functional
- Schema quality: unverified → good ▲ functional
- Licence: MIT functional
1 Aug 26 +31
- Malware scan: unverified → pass ▲ security
- Tool coverage: unverified → 100 ▲ functional
31 Jul 26 −1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
30 Jul 26 −40
- Malware scan: pass → unverified ▼ security
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
27 Jul 26 46

First indexed and scored.

Show 2 earlier entries Hide earlier entries

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 4 Aug 2026 · Analysed npm/@cocaxcode/[email protected]

Provenance none

Ecosystem: npm · Outcome: none

Dependencies 96 packages

96 packages in the resolved dependency tree · 96 deprecated · 29 stale.

The dependency tree was only partially resolved, so these counts may be incomplete.

MCP tools — 32 exposed · ~1,938 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.

Tool Tokens

df_assign ~48

Asignar un issue al usuario actual. Si el issue ya tiene asignado, no hace nada.

Input Output Examples

Name	Type	Req	Description
issueKey	string	yes	Clave del issue (ej: PROJ-123)

No output schema declared.

No examples provided.

df_branch ~117

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.

Input Output Examples

Name	Type	Req	Description
confirm	boolean	—	true para crear la branch
description	string	yes	Descripcion corta en kebab-case (ej: add-login)
issueKey	string	yes	Clave del issue de Jira (ej: PROJ-123)
type	string	yes	Tipo de branch: feat o fix

No output schema declared.

No examples provided.

df_checkout ~37

Cambiar a una rama existente. Verifica que no haya cambios sin pushear antes.

Input Output Examples

Name	Type	Req	Description
branch	string	yes	Nombre de la rama

No output schema declared.

No examples provided.

df_comment ~68

Añadir un comentario a un issue de Jira. Requiere confirm: true para ejecutar.

Input Output Examples

Name	Type	Req	Description
body	string	yes	Texto del comentario
confirm	boolean	—	true para publicar el comentario
issueKey	string	yes	Clave del issue (ej: PROJ-123)

No output schema declared.

No examples provided.

df_find_branch ~60

Buscar si existe una rama local o remota que contenga un issue key (ej: PROJ-123). Devuelve la rama si existe o null.

Input Output Examples

Name	Type	Req	Description
issueKey	string	yes	Clave del issue (ej: PROJ-123)

No output schema declared.

No examples provided.

df_flow_create ~100

Crear un nuevo flow (playbook) con nombre, disparador y pasos. El AI lo ejecuta cuando el usuario dice algo que matchea el trigger.

Input Output Examples

Name	Type	Req	Description
name	string	yes	Nombre del flow (ej: pr-ready)
steps	array	yes	Pasos del flow: [{tool, confirm?, target?, note?}]
trigger	string	yes	Descripcion del disparador (ej: cuando el usuario dice "PR listo")

No output schema declared.

No examples provided.

df_flow_delete ~52

Eliminar un flow. El flow "start-task" requiere confirm: true.

Input Output Examples

Name	Type	Req	Description
confirm	boolean	—	true para confirmar eliminacion del flow default
name	string	yes	Nombre del flow a eliminar

No output schema declared.

No examples provided.

df_flow_get ~36

Ver el detalle completo de un flow (nombre, disparador y todos los pasos).

Input Output Examples

Name	Type	Req	Description
name	string	yes	Nombre del flow

No output schema declared.

No examples provided.

df_flow_list ~26

Listar todos los flows configurados con nombre, disparador y numero de pasos.

Input Output Examples

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

df_flow_update ~54

Modificar un flow existente: cambiar disparador y/o pasos.

Input Output Examples

Name	Type	Req	Description
name	string	yes	Nombre del flow a modificar
steps	array	—	Nuevos pasos
trigger	string	—	Nuevo disparador

No output schema declared.

No examples provided.

df_issue ~44

Obtener el detalle completo de un issue de Jira. Solo lectura, sin efectos secundarios.

Input Output Examples

Name	Type	Req	Description
issueKey	string	yes	Clave del issue (ej: PROJ-123)

No output schema declared.

No examples provided.

df_issues ~67

Listar mis issues asignados en Jira. Soporta filtros opcionales por proyecto y estado.

Input Output Examples

Name	Type	Req	Description
project	string	—	Filtrar por clave de proyecto (ej: PROJ)
status	string	—	Filtrar por estado (ej: "To Do", "In Progress")

No output schema declared.

No examples provided.

df_merge ~65

Mergear una rama en la rama actual. Requiere confirm: true. Si hay conflictos, los reporta sin abortar.

Input Output Examples

Name	Type	Req	Description
branch	string	yes	Nombre de la rama a mergear en la rama actual
confirm	boolean	—	true para ejecutar el merge

No output schema declared.

No examples provided.

df_pr ~54

Crear un Pull Request (GitHub) o Merge Request (GitLab) para la rama actual.

Input Output Examples

Name	Type	Req	Description
body	string	—	Descripcion del PR/MR
title	string	yes	Titulo del PR/MR

No output schema declared.

No examples provided.

df_project_delete ~28

Eliminar un proyecto configurado.

Input Output Examples

Name	Type	Req	Description
name	string	yes	Nombre del proyecto a eliminar

No output schema declared.

No examples provided.

df_project_list ~17

Listar todos los proyectos configurados.

Input Output Examples

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

df_project_setup ~225

Configurar un nuevo proyecto: vincula Jira + Git provider. Auto-detecta tipo de Jira, version API, provider Git y rama base.

Input Output Examples

Name	Type	Req	Description
gitProject	string	—	Path completo del proyecto en GitLab (ej: grupo/subgrupo/repo). Util cuando el remote es un fork pero se quiere vincular al proyecto principal.
gitToken	string	yes	Token de GitHub o GitLab
gitUrl	string	—	URL base del GitLab self-hosted (ej: https://gitlab.empresa.com). Si no se pasa, se extrae del remote.
jiraEmail	string	—	Email para Jira Cloud
jiraPat	string	—	Personal Access Token para Jira Server
jiraProjectKey	string	yes	Clave del proyecto en Jira (ej: PROJ, DEV, BACK)
jiraToken	string	—	API Token para Jira Cloud
jiraUrl	string	yes	URL de Jira (ej: https://myteam.atlassian.net)
name	string	yes	Nombre del proyecto

No output schema declared.

No examples provided.

df_project_switch ~25

Cambiar el proyecto activo.

Input Output Examples

Name	Type	Req	Description
name	string	yes	Nombre del proyecto

No output schema declared.

No examples provided.

df_project_update ~173

Modificar la configuracion de un proyecto existente.

Input Output Examples

Name	Type	Req	Description
baseBranch	string	—	Rama base (main/master)
gitProject	string	—	Path completo del proyecto en GitLab (ej: grupo/subgrupo/repo)
gitToken	string	—	Nuevo token de Git provider
gitUrl	string	—	URL base del GitLab self-hosted (ej: https://gitlab.empresa.com)
jiraEmail	string	—	Nuevo email para Jira Cloud
jiraPat	string	—	Nuevo PAT para Jira Server
jiraProjectKey	string	—	Nueva clave del proyecto en Jira
jiraToken	string	—	Nuevo API Token para Jira Cloud
jiraUrl	string	—	Nueva URL de Jira
name	string	yes	Nombre del proyecto a modificar

No output schema declared.

No examples provided.

df_pull ~19

Hacer pull de la rama actual desde el remote.

Input Output Examples

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

df_push ~44

Hacer push de la rama actual al remote. Requiere confirm: true para ejecutar. Sin confirm devuelve preview.

Input Output Examples

Name	Type	Req	Description
confirm	boolean	—	true para ejecutar el push

No output schema declared.

No examples provided.

df_rule_create ~96

Crear una regla configurable. Las reglas pueden bloquear o advertir sobre acciones.

Input Output Examples

Name	Type	Req	Description
action	string	yes	Accion: block (bloquea) o warn (solo avisa)
description	string	yes	Descripcion de lo que hace la regla
name	string	yes	Nombre de la regla (ej: no-merge-to-main)
scope	string	yes	Ambito: git, jira, o all

No output schema declared.

No examples provided.

df_rule_delete ~27

Eliminar una regla.

Input Output Examples

Name	Type	Req	Description
name	string	yes	Nombre de la regla a eliminar

No output schema declared.

No examples provided.

df_rule_get ~28

Ver el detalle completo de una regla.

Input Output Examples

Name	Type	Req	Description
name	string	yes	Nombre de la regla

No output schema declared.

No examples provided.

df_rule_list ~26

Listar todas las reglas configuradas con su estado (activada/desactivada).

Input Output Examples

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

df_rule_project_add ~63

Añadir una regla propia que solo aplica al proyecto actual.

Input Output Examples

Name	Type	Req	Description
action	string	yes	Accion
description	string	yes	Descripcion de la regla
name	string	yes	Nombre de la regla
scope	string	yes	Ambito

No output schema declared.

No examples provided.

df_rule_project_override ~66

Activar o desactivar una regla global para el proyecto actual. El override solo aplica a este proyecto.

Input Output Examples

Name	Type	Req	Description
enabled	boolean	yes	true para activar, false para desactivar en este proyecto
ruleName	string	yes	Nombre de la regla global a sobreescribir

No output schema declared.

No examples provided.

df_rule_project_remove ~39

Eliminar una regla propia del proyecto actual o quitar un override de regla global.

Input Output Examples

Name	Type	Req	Description
name	string	yes	Nombre de la regla a eliminar

No output schema declared.

No examples provided.

df_rule_toggle ~43

Activar o desactivar una regla.

Input Output Examples

Name	Type	Req	Description
enabled	boolean	yes	true para activar, false para desactivar
name	string	yes	Nombre de la regla

No output schema declared.

No examples provided.

df_rule_update ~56

Modificar una regla existente.

Input Output Examples

Name	Type	Req	Description
action	string	—	Nueva accion
description	string	—	Nueva descripcion
name	string	yes	Nombre de la regla a modificar
scope	string	—	Nuevo ambito

No output schema declared.

No examples provided.

df_statuses ~51

Listar las transiciones disponibles para un issue (los estados a los que se puede mover desde su estado actual).

Input Output Examples

Name	Type	Req	Description
issueKey	string	yes	Clave del issue (ej: PROJ-123)

No output schema declared.

No examples provided.

df_transition ~84

Mover un issue a un nuevo estado. Requiere confirm: true para ejecutar. Sin confirm devuelve preview.

Input Output Examples

Name	Type	Req	Description
confirm	boolean	—	true para ejecutar la transicion
issueKey	string	yes	Clave del issue (ej: PROJ-123)
transitionId	string	yes	ID de la transicion (obtenido de df_statuses)

No output schema declared.

No examples provided.

On this page

Handy links

Scoring key

80+ high trust
60–79 medium
below 60 low

How we score

Score history · last 30 days

27 Jul 4 Aug