jira-stories
Related Servers
Alternatives to jira-stories
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceEnables Claude Code CLI to interact with Jira, including fetching issue details, searching issues with JQL, retrieving comments, and getting user info, with support for multiple Jira environments.-
- AlicenseAqualityDmaintenanceEnables logging time entries to Jira Cloud issues, including adding worklogs, listing existing entries, and verifying credentials.3MIT
- AlicenseAqualityCmaintenanceEnables Claude Code to interact with JIRA through natural language, supporting issue creation, updates, searches, and workflow transitions, designed for enterprise intranets.2260 npmApache 2.0
- AlicenseAqualityDmaintenanceEnables interaction with Jira issues via JQL search, epic management, comments, attachments, and issue CRUD, with support for both Cloud and Server/Data Center instances.97 npmMIT
- AlicenseBqualityCmaintenanceEnables control and interaction with Jira through the Jira Command Line interface, allowing users to manage Jira tasks and operations through natural language commands.37MIT
- AlicenseAqualityCmaintenanceEnables VS Code Copilot to interact with your Jira instance—Cloud, Server, or Data Center—through natural language for issue search, creation, updates, comments, transitions, assignments, project listing, and user profile lookup.1060 npmApache 2.0
TDQS
Scored across 7 tools
Most tools target clearly distinct actions: list projects, get metadata, search issues, preview, create, and update. The main potential confusion is between jira_get_create_fields and jira_preview_issue, since both relate to issue creation fields, though one describes the schema and the other previews actual values.
Every tool follows the same jira_<verb>_<noun> pattern using snake_case. The verbs are clear and consistently used, making the tool set highly predictable.
Seven tools is well-scoped for a Jira issue creation/update workflow. Each tool serves a necessary step in the process without unnecessary redundancy.
The workflow covers project discovery, issue type/field metadata, duplicate checking, preview, creation, and update. A direct get-single-issue tool is missing but search can serve that purpose, and deeper Jira lifecycle operations like transitions are outside the apparent scope.