Devflow Mcp
Sync Jira issues with GitHub or GitLab branches, PRs, and delivery flows so your agent can keep tickets and code aligned.
Overview
io.github.cocaxcode/devflow-mcp is a MCP server for the Build phase that links Jira Cloud or Server with GitHub/GitLab for branches, issues, PRs, and dev flows.
What is this MCP server?
- Bridges Jira (Cloud and Server) with GitHub and GitLab
- Tools for branches, issues, pull requests, and flow-oriented dev actions
- stdio npm package @cocaxcode/devflow-mcp (v0.1.8)
- Reduces copy-paste between ticket comments and git state during agent sessions
- GitHub repository cocaxcode/devflow-mcp under standard MCP server schema
- Jira Cloud and Jira Server supported
- GitHub and GitLab integrations
- Package @cocaxcode/devflow-mcp v0.1.8
Community signal: 1 GitHub stars.
What problem does it solve?
Solo builders lose traceability when Jira tickets and git branches diverge and the agent cannot see either system.
Who is it for?
Small teams or solo devs on Jira plus GitHub/GitLab who want agent-assisted ticket-to-PR hygiene during active Build sprints.
Skip if: Builders on Linear-only or Notion-only stacks with no Jira, or orgs without API access to their git host.
What do I get? / Deliverables
After setup, your agent can coordinate Jira and GitHub/GitLab workflow actions so work items and code changes stay linked.
- Agent-driven coordination between Jira work items and git branches or PRs
- Fewer manual updates when moving tickets through Build
- Queryable dev flow state across issue tracker and repository
Recommended MCP Servers
Journey fit
Issue-to-repo orchestration sits in Build as how solo builders (or tiny teams) run delivery without a separate PM bot. PM subphase fits linking backlog items, branches, and pull requests across Jira Cloud or Server and Git hosts.
How it compares
Jira–Git MCP bridge for delivery flows, not a standalone code review skill or a CI pipeline host.
Common Questions / FAQ
Who is io.github.cocaxcode/devflow-mcp for?
It is for developers using Jira alongside GitHub or GitLab who want their coding agent to manage issue and PR alignment through MCP.
When should I use io.github.cocaxcode/devflow-mcp?
Use it during Build when you are cutting branches from tickets, opening PRs, or tracing status across Jira and your git remote.
How do I add io.github.cocaxcode/devflow-mcp to my agent?
Install @cocaxcode/devflow-mcp via npm, add stdio MCP config with Jira and GitHub or GitLab credentials in env vars, and restart your agent.