troylar/jira-mcp-server

0Stars on the repository
10Mods indexed here, across every type
9mo agoLast push, which is what freshness is scored on
MITLicence, which decides whether bodies are shown

speckit.analyze

01

troylar/jira-mcp-server

Command Claude Code

Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.

not rated 0 9mo ago A 26 tokens copy · 100% MIT

speckit.checklist

02

troylar/jira-mcp-server

Command Claude Code

Generate a custom checklist for the current feature based on user requirements.

not rated 0 9mo ago A 13 tokens copy · 88% MIT

speckit.clarify

03

troylar/jira-mcp-server

Command Claude Code

Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.

not rated 0 9mo ago A 27 tokens copy · 98% MIT

troylar/jira-mcp-server

Command Claude Code

Create or update the project constitution from interactive or provided principle inputs, ensuring all dependent templates stay in sync.

not rated 0 9mo ago A 20 tokens copy · 95% MIT

speckit.implement

05

troylar/jira-mcp-server

Command Claude Code

Execute the implementation plan by processing and executing all tasks defined in tasks.md.

not rated 0 9mo ago A 14 tokens copy · 92% MIT

speckit.plan

06

troylar/jira-mcp-server

Command Claude Code

Execute the implementation planning workflow using the plan template to generate design artifacts.

not rated 0 9mo ago A 14 tokens copy · 84% MIT

speckit.specify

07

troylar/jira-mcp-server

Command Claude Code

Create or update the feature specification from a natural language feature description.

not rated 0 9mo ago A 13 tokens copy · 69% MIT

speckit.tasks

08

troylar/jira-mcp-server

Command Claude Code

Generate an actionable, dependency-ordered tasks.md for the feature based on available design artifacts.

not rated 0 9mo ago A 18 tokens copy · 92% MIT

At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: