# Jira Software Cloud MCP for AI Agents AI Agent Connect > Jira Software Cloud lets your AI agent handle your Agile workflows. You can list boards, track sprints, manage backlogs, and inspect epics without leaving your workspace. It turns your AI into a project management assistant that knows your Jira setup inside out. ## Overview - **Category:** industry-titans - **Price:** Free - **Endpoint:** https://edge.vinkius.com/vk_preview_pIquAtHFeHLdgJuJVu2P6nteoAaXYoCxQuZ7gqmD/ai-agent-connect - **Tags:** agile, scrum, kanban, sprint-planning, issue-tracking ## Description Imagine you're in the middle of a deep coding session and realize a ticket's priority just shifted. Instead of context-switching to a browser, hunting through boards, and clicking through menus, you just tell your agent to handle it. This Connector bridges that gap, letting your AI client interact directly with your Jira Software Cloud instance. It understands the nuances of Agile project management, from the way your sprints are structured to how your story points are distributed across the backlog. You can ask it to pull up the current status of a specific epic or move a batch of issues into the next sprint while you stay focused on your actual work. It handles the tedious data entry and status checking that usually eats up your day. By connecting this to your existing setup through Vinkius, you get a way to manage your team's progress through natural conversation. It's about making the project management side of your job feel less like a chore and more like a quick check-in. You can query your backlog to see what's next, check build statuses to see if the latest code is live, or even update your sprint goals on the fly. It takes the friction out of keeping your project organized, moving the focus back to the work that actually matters. ## Tools ### get_board_sprints See all the sprints associated with a board. Use this to track historical and upcoming work. ### get_build Fetch the latest build data from your Jira instance. This helps you monitor continuous integration. ### get_deployment_gating_status Check if a deployment is currently blocked or cleared. This is vital for release management. ### get_epic Get the specific details of a single epic. Use this to see the high-level requirements and goals. ### get_issue_estimation Check how many story points are assigned to a task. This helps you monitor team capacity. ### get_repository_dev_info Pull development information from your connected repository. It links your code to your Jira tasks. ### get_sprint_issues List all the tasks currently assigned to a specific sprint. This is the best way to see what the team is doing now. ### get_sprint Fetch the details of a specific sprint. Use this to see the start date, end date, and goal. ### link_security_workspaces Connect security workspaces to your Jira instance. This helps organize security-related tasks. ### move_issues_to_backlog Push tasks back into the backlog. Use this when work is deprioritized or needs to be reconsidered. ### rank_epics Reorder the priority of your epics. This helps you focus on the most important project goals first. ### rank_issues Change the order of issues in a list or board. This lets you quickly prioritize the next tasks. ### set_issue_estimation Update the story points for a specific issue. Use this to adjust your plan as requirements change. ### move_issues_to_epic Assign a group of issues to a specific epic. This keeps your project structure organized. ### store_dev_info Save development information to your Jira instance. This keeps your project data in sync with your code. ### submit_builds Send new build data to Jira. This is great for keeping your team updated on the latest CI results. ### submit_deployments Push deployment data into your Jira instance. Use this to track where your code is currently live. ### submit_feature_flags Send feature flag status to Jira. This helps you track what features are active for users. ### create_board Create a new board with a specific name and type. This helps you set up new project spaces quickly. ### get_epic_issues Fetch all issues associated with a specific epic. Use this to see the full scope of a large project. ### submit_vulnerabilities Send vulnerability data to your Jira instance. It helps keep security issues organized. ### get_board_configuration Pull the settings and layout of a specific board. This is useful for understanding how a team organizes its work. ### move_issues_to_sprint Shift multiple issues into a specific sprint. This makes it easy to plan work for the upcoming cycle. ### create_sprint Generate a new sprint container. You can use this to start a new development phase. ### get_agile_issue Retrieve an issue along with its specific Agile fields. This gives you a complete picture of a task's status. ### get_board_backlog Pull the list of issues currently in the backlog. It helps you see what's waiting to be started. ### get_board_epics List all the epics tied to a specific board. This gives you a high-level view of project goals. ### list_boards Get a complete list of all boards in your Jira Software instance. This is your starting point for navigation. ### submit_incidents Report incidents or reviews to your Jira instance. This keeps your support and ops teams informed. ### submit_remote_links Send remote link data to Jira. This helps you keep external resources connected to your tasks. ### update_sprint Change a sprint's state to active or closed. Use this to move the team into the next phase of work. ## Prompt Examples **Prompt:** ``` What's the status of the current sprint? ``` **Response:** ``` ### Current Sprint Status **Sprint Name:** Mobile App Refresh **Goal:** Finalize login flow and user profile setup | Status | Issue | Owner | | :--- | :--- | :--- | | ✅ Done | Fix login bug | Sarah | | 🏗️ In Progress | Update splash screen | Mike | | ⏳ To Do | Add social login | Elena | *The team is currently 60% through the sprint goals.* ``` **Prompt:** ``` Move all the High priority bugs to the next sprint. ``` **Response:** ``` I've identified 4 issues marked as 'High' priority bugs in your current backlog. I am moving them to the next available sprint now. **Moved Issues:** - BUG-102: Crash on startup - BUG-105: API timeout - BUG-109: Image upload failure - BUG-112: Password reset loop *Success! Your next sprint is now updated with these high-priority items.* ``` **Prompt:** ``` Give me a summary of the Mobile App epic. ``` **Response:** ``` ### Epic: Mobile App Refresh **Description:** Overhauling the core user experience for the mobile platform. **Progress Summary:** - **Total Issues:** 24 - **Completed:** 12 - **In Progress:** 5 - **Backlog:** 7 **Key Tasks Remaining:** - Biometric authentication - Dark mode support - Push notification overhaul ``` ## Capabilities ### Create new boards Set up new Scrum or Kanban boards for different project types instantly. ### Manage sprint cycles Start and finish sprints to track your team's progress over time. ### Reorder priorities Rank issues and epics to change the order of work as requirements shift. ### Update story points Adjust issue estimations as soon as your project scope changes. ### Pull dev data Get build and deployment data for your projects directly in your chat. ### Shift issues Move items between your backlog and active sprints with simple commands. ## Use Cases ### The Sprint Planning Refresh A Scrum Master needs to move 10 tickets into the next sprint. They ask the agent to move issues to sprint, and it happens instantly. ### The Quick Status Check A developer wants to know the status of a build. They ask the agent to get build, and it reports the latest success. ### The Epic Cleanup A PM wants to see all issues for a specific epic. They ask the agent to get epic issues to see what's left to do. ### The Priority Shift A sudden bug comes in. The user asks the agent to rank issues, and it moves the high-priority fix to the top of the board. ## Benefits - Stop manual status updates by using update_sprint to move your team into new phases automatically. - Keep your priorities straight by using rank_issues and rank_epics to reorder work without clicking through the UI. - Get a clear view of your capacity by using get_issue_estimation and set_issue_estimation to manage story points. - Stay in your IDE by using get_repository_dev_info to see how your code relates to your Jira tickets. - Monitor your release cycle more closely using submit_builds and submit_deployments to track live updates. - Organize your work better by using move_issues_to_epic and move_issues_to_sprint to keep your backlog clean. ## How It Works The bottom line is you get a way to handle Jira tasks through your AI client without ever opening a browser. 1. Subscribe to the Jira Software Cloud MCP on Vinkius 2. Input your Jira Domain, Email, and API Token 3. Ask your AI client to list boards or update sprint statuses ## Frequently Asked Questions **Can I use the Jira Software Cloud MCP to manage my Scrum boards?** Yes, it lets you list boards, see configurations, and manage sprints directly through your AI client. **How does the Jira Software Cloud MCP help with sprint planning?** It allows you to create sprints, move issues, and update story points quickly without needing to navigate the web interface. **Can my AI agent update Jira story points?** Yes, it can get and set issue estimations to keep your team's velocity accurate as project requirements change. **Does the Jira Software Cloud MCP support Kanban boards?** Yes, it can manage both Scrum and Kanban board configurations, making it versatile for different team structures. **Can I use this to track my builds and deployments?** Yes, it can pull build data and deployment gating status to keep you informed on the status of your code. **How do I move issues to an epic using the Jira Software Cloud MCP?** You can simply ask your AI agent to move specific issues to the desired epic, and it will handle the update for you. **How do I view the backlog for a specific board?** Use the `get_board_backlog` tool with the target `boardId`. It will return all issues currently in the backlog for that Scrum or Kanban board. **Can I change a sprint's status to active or closed?** Yes, use the `update_sprint` tool and provide the `sprintId` along with the desired `state` ('active' or 'closed'). **Is it possible to check the story point estimation for an issue?** Yes! The `get_issue_estimation` tool allows you to retrieve the estimation value for any specific agile issue using its ID.