Sign In

@cocaxcode/devflow-mcp

Package Overview
Dependencies
Maintainers
1
Versions
16
Alerts
File Explorer

Advanced tools

License
Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

@cocaxcode/devflow-mcp - npm Package Compare versions

Comparing version
0.1.4
 to
0.1.5
+1
-1
package.json
{
"name": "@cocaxcode/devflow-mcp",
"version": "0.1.4",
"version": "0.1.5",
"mcpName": "io.github.cocaxcode/devflow-mcp",

@@ -5,0 +5,0 @@ "description": "MCP server that connects Jira (Cloud + Server) with GitHub/GitLab to automate your dev workflow. Branch creation, issue transitions, PR/MR generation, and custom flow playbooks — all from your AI assistant.",

+6
-8
README.md

@@ -40,5 +40,5 @@ <p align="center">

devflow-mcp is an MCP server that connects Jira (Cloud + Server) with GitHub/GitLab (cloud + self-hosted) through 32 tools your AI assistant can call directly. It auto-detects your Jira version and git provider, enforces configurable safety rules, and lets you define custom YAML flow playbooks for repeatable workflows.
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.
No context switching. No browser tabs. Just tell your assistant what you need.
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, and credentials. Switch between projects mid-conversation. **All credentials stay local in `~/.dfm/` — nothing is synced, nothing is tracked, nothing leaves your machine.**

@@ -383,8 +383,8 @@ ---

All data lives in `~/.dfm/`:
Everything lives in `~/.dfm/` — your home directory, never inside any git repository. Jira tokens, GitHub PATs, GitLab tokens — all stored locally with `600` permissions (owner-only read/write). Nothing gets committed, nothing gets pushed, nothing leaves your machine.
```
~/.dfm/
├── projects/ # Project configs (.json)
│ ├── my-project.json
├── projects/ # Project configs (.json) — credentials included
│ ├── my-project.json # Jira URL, token, GitHub PAT, branch rules
│ └── other-project.json

@@ -402,6 +402,4 @@ ├── flows/ # Flow definitions (.yaml)

Project files are created with `600` permissions (owner-only read/write).
**Project resolution works automatically:** devflow-mcp matches your current working directory against each project's `paths`. If no match, it falls back to the project set via `df_project_switch`. If neither works, it prompts you to configure with `df_project_setup`. 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.
> **Tip:** **Project resolution:** devflow-mcp matches your current working directory against each project's `paths`. If no match, it falls back to the project set via `df_project_switch`. If neither works, it prompts you to configure with `df_project_setup`.
---

@@ -408,0 +406,0 @@ 

dist/index.js

Sorry, the diff of this file is too big to display