A
licenseNot graded
qualityB
maintenanceEnables AI assistants to manage Jira issues and Confluence pages, including creating, updating, searching, commenting, and transitioning work items through natural language.
MIT
devflow
by cocaxcode
Related Servers
Alternatives to devflow
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables AI assistants to interact with Atlassian Cloud (Jira, Confluence, Bitbucket) through natural language, providing CRUD operations for issues, pages, pull requests, and more.869 npmMIT
- AlicenseNot gradedqualityFmaintenanceEnables AI assistants to manage Jira projects, issues, sprints, and boards via natural language.43 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables end-to-end automation of developer workflows from Jira issue tracking to GitHub pull requests through natural language, allowing developers to search issues, create branches, commit changes, and manage PRs directly from their IDE.2MIT
- FlicenseNot gradedqualityBmaintenanceEnables AI agents to manage Jira and Confluence directly, including issue tracking, sprint management, and knowledge base operations through natural language.-
- AlicenseCqualityDmaintenanceEnables AI assistants to manage Jira Cloud projects, issues, sprints, and more through a curated set of 62 tools covering the full lifecycle of stories, epics, bugs, and sprints.62GPL 3.0
TDQS
B3.2/5.0
Scored across 32 tools
Disambiguation4/5
Most tools target a distinct resource and action, such as df_pull vs df_push or df_issue vs df_issues. The main ambiguity is in the rule family, especially df_rule_project_add, df_rule_project_override, and df_rule_project_remove, whose boundaries overlap more than the others.
Naming Consistency3/5
All tools share the df_ prefix and snake_case, but the action placement is mixed: git/issue tools tend to be action-first (df_pull, df_assign, df_checkout), while flows/rules/projects use resource-first names (df_flow_create, df_rule_update, df_project_setup). This is readable but not a single consistent pattern.
Tool Count2/5
32 tools is a large surface, and while it spans several domains, the rule subsystem alone has 9 tools with significant overlap. This feels heavier than needed and could be consolidated without losing capability.
Completeness2/5
Project, flow, and rule lifecycles are mostly covered, and Jira transitions/assign/comment support common workflow actions. However, there is no git commit or status tool, which creates a dead end in a standard branch-commit-push-PR flow, and Jira issue creation/update is also missing.
Maintenance
ActivityInactive
ResponsivenessNo issues