Cache Jira project metadata to reduce repeated Atlassian MCP calls.
npx skills add https://github.com/rnagrodzki/sdlc-marketplace --skill jira-sdlc
Please help me install this Agent Skill. Skill: jira-sdlc Source: https://github.com/rnagrodzki/sdlc-marketplace/tree/main/plugins/sdlc-utilities/skills/jira-sdlc Command: npx skills add https://github.com/rnagrodzki/sdlc-marketplace --skill jira-sdlc
Jira users need to manage many projects across tenants, and repeated Atlassian MCP calls slow down operations; this skill caches project metadata to speed up Jira actions and reduce API churn.
Install and activate the jira-sdlc skill, then provide a --project key to initialize the cache and begin performing Jira operations with cached metadata.
High-intent search queries and answers about installing and using this skill.
To reduce repeated Atlassian MCP calls, cache Jira project metadata like cloudId, issue types, and field schemas. This approach speeds up Jira actions across multiple projects and minimizes API churn by using validated cache data instead of live lookups.
You can manage Jira workflows across multiple tenants by caching site URLs and project metadata. The cache supports multi-project configurations and optional site disambiguation to map actions accurately to different Jira tenants.
To create and transition Jira issues without guessing field IDs, use validated cache data containing field schemas and workflows. The cache applies strict MCP parameter shapes derived from issue types and link types, ensuring accurate transitions and issue creation.
For fast MCP issue search and assignment, cache cloudId, siteUrl, project metadata, issue types, field schemas, workflows, link types, and user mappings. Validated cache data ensures correct user mappings and efficient issue searches.
This Jira automation approach supports applying standardized templates for new issues. It uses cached field schemas and placeholders to generate standardized descriptions, ensuring new issues adhere to consistent formatting and workflow requirements.
A limitation of caching Jira metadata for MCP workflows is the reliance on strict parameter shapes, meaning operations require pre-validated cache data for issue types and workflows. The cache must be initialized with a project key before performing any actions.
HaywardMoriharaView, create, update, and manage Jira issues and sprints via CLI and MCP backends.
aydendenAutomate Jira issue management via the Atlassian CLI.
chloebrettPackage MCP servers into standalone .mcpb archives with dependencies and configuration.
ValerianGuivarchSummarize Jira ticket details from the IDF project via MCP.
