# Jira Software Cloud MCP > Jira Software Cloud MCP connects your agent directly to your Jira instance, letting you manage Agile workflows without ever opening the browser. You can list boards, track sprints, inspect backlogs, and move issues across epics or sprints using natural language commands. ## Overview - **Category:** industry-titans - **Price:** Free - **Tags:** agile, scrum, kanban, sprint-planning, issue-tracking ## Description Need to keep up with complex project progress? This MCP gives your AI client deep access to everything happening in Jira Software Cloud. Forget switching between dashboards and tabs; you manage the entire agile lifecycle—from initial ideas to final deployment—all through conversation. Your agent can automatically list boards, fetch all associated sprints, or find every issue linked to a specific epic. Need to adjust priorities? You can query backlogs, update issue estimations, or even submit build status and feature flag data. This integration makes Jira's complex backend logic available directly where you work. All this power is managed through Vinkius, giving your AI client one central place to access thousands of industry tools. ## Tools ### create_board This tool creates a new Scrum or Kanban board for the project. ### get_epic_issues Lists every single issue that belongs under a given epic container. ### submit_vulnerabilities Records details about security vulnerabilities found during testing or review. ### get_board_configuration Retrieves settings and structure details for any existing project board. ### move_issues_to_sprint Moves selected issues into an active or planned sprint timeline. ### create_sprint It sets up and launches an entirely new sprint timeline within Jira. ### get_agile_issue Retrieves detailed information about a specific issue, including all agile fields like story points. ### get_board_backlog Fetches the list of issues currently waiting in a board's backlog. ### get_board_epics Shows all the large, overarching feature groups (epics) attached to a specific board. ### get_board_sprints Lists every sprint that has ever been associated with this project board. ### get_build Retrieves current build status and details for the software repository. ### get_deployment_gating_status Checks if a feature is ready to deploy by checking defined gate requirements. ### get_epic Retrieves comprehensive details for a specific, high-level project epic. ### get_issue_estimation Checks the current story point estimation assigned to any individual issue. ### get_repository_dev_info Gathers general development information from the associated code repository. ### get_sprint_issues Shows all issues that are currently assigned to a specific, active sprint. ### get_sprint Retrieves the full details and status of any given sprint timeline. ### link_security_workspaces Connects or links necessary security workspaces required for project access. ### list_boards Gets a list of every board available across the entire Jira Software instance. ### move_issues_to_backlog Moves one or more selected issues back into the general backlog queue. ### move_issues_to_epic Assigns a group of issues to a specific parent epic container. ### rank_epics Adjusts the relative priority ranking of multiple epics against each other. ### rank_issues Sets or changes the priority order for a list of individual issues. ### set_issue_estimation Assigns or updates the story point estimate for an issue. ### store_dev_info Saves development information, like version numbers, to Jira for tracking. ### submit_builds Reports and submits build data, indicating when a new code compilation is ready. ### submit_deployments Logs the successful completion of a software deployment to an environment. ### submit_feature_flags Reports the status of feature flags, indicating if code features are live or hidden. ### submit_incidents Records details about system incidents or formal reviews that occurred during development. ### submit_remote_links Adds links to external documentation or resources relevant to the issue. ### update_sprint Changes the status of a sprint, marking it as active or completed. ## Prompt Examples **Prompt:** ``` List all available Jira boards. ``` **Response:** ``` I've found 3 boards: 'Mobile App' (ID: 1), 'Web Backend' (ID: 2), and 'Marketing' (ID: 3). Which one would you like to explore? ``` **Prompt:** ``` Show me the issues in the backlog for board 1. ``` **Response:** ``` Retrieving backlog for 'Mobile App'... I found 12 issues. The top items are 'Fix login bug' and 'Update splash screen'. Would you like more details on any of these? ``` **Prompt:** ``` What is the estimation for issue 10123? ``` **Response:** ``` The estimation for issue 10123 is currently set to 5 story points. ``` ## Capabilities ### Manage project boards List and fetch configurations for all Scrum and Kanban boards in your account. ### Control sprints and timelines Create new sprints, retrieve details, or update a sprint's status to start or close it. ### Audit issue backlogs and epics Query the backlog for specific boards, retrieve all associated epics, and track issues within those large feature sets. ### Track development progress (DevOps) Get build data, submit deployment statuses, or record feature flags to see real-time system health. ### Adjust issue priorities and status Move issues between backlogs, epics, or sprints, and set story point estimations for accurate velocity tracking. ## Use Cases ### The PM needs to pivot the roadmap quickly. A Product Manager realizes Epic 'Payment Gateway' is stalled. They ask their agent, and it uses `get_board_epics` to identify the bottleneck component. It then calls `rank_epics`, moving that epic down and prioritizing a lower-risk area using `move_issues_to_epic`. The PM gets an immediate status report and a revised plan. ### The Scrum Master needs to close out the quarter. It's time for sprint review. The agent uses `get_board_sprints` to identify all completed sprints, then calls `update_sprint` on them all simultaneously. It also runs `get_build` and `submit_incidents` to log final data before declaring the quarter finished. ### The Developer needs to verify release readiness. Before merging, a developer asks their agent about deployment status. The agent checks `get_deployment_gating_status`, then retrieves development info with `get_repository_dev_info`. If everything is green, the process continues. ### The QA team needs to audit outstanding work. QA wants to know what issues are floating in limbo. They ask their agent, which uses `get_board_backlog` to pull all pending tickets and then calls `get_issue_estimation` on the top five items so they can report readiness. ## Benefits - Stop manually checking progress. Your agent can call `get_board_sprints` to instantly list all active timelines, giving you a real-time status overview without opening the board UI. - Keep your team moving by using `create_sprint` and `update_sprint`. You can initiate or close sprints with a single command, ensuring sprint boundaries are always accurate. - Improve planning depth. Instead of guessing priorities, you can use `get_board_backlog` to pull the full list of pending work, then use `rank_issues` to instantly adjust the order for the dev team. - Streamline DevOps tracking. Your agent handles critical release data: submitting builds via `submit_builds`, logging deployments with `submit_deployments`, and even reporting feature flag status using `submit_feature_flags`. - Deepen your visibility into features. By calling `get_board_epics` and then `get_epic_issues`, you get a complete audit trail of every piece of work contributing to a major product goal. ## How It Works The bottom line is that your AI client acts as an automated layer on top of your existing Jira workflows, letting you execute complex tasks with simple text prompts. 1. First, subscribe to this MCP and provide your Jira Domain, Email, and API Token. 2. Next, connect the credentials to your preferred AI client like Cursor or Claude. Your agent now has permission to read and write data in your workspace. 3. Finally, you instruct your agent using natural language—for example, 'Start a new sprint for the Mobile App board'—and it executes the necessary Jira operations. ## Frequently Asked Questions **How do I check which issues are part of an epic using Jira Software Cloud MCP?** You use the `get_epic_issues` tool. This function takes an Epic ID and returns a comprehensive list of every issue that belongs under it, letting you audit the scope immediately. **Can I automatically start or end a sprint with Jira Software Cloud MCP?** Yes, use the `update_sprint` tool. You can pass instructions to change the sprint's state—marking it active or closed—without needing access to the UI. **Does this MCP help with DevOps tracking for my project?** Absolutely. The MCP provides tools like `get_build` and `submit_deployments`. You can track build status, submit deployment logs, and check feature flag settings from your agent. **What if I need to change the priority of a bunch of issues?** You use the `rank_issues` tool. Simply tell your agent which issues you want to rank and in what order, and it updates them across the board. **Can Jira Software Cloud MCP help me organize tickets into a new epic?** Yes. You use `move_issues_to_epic`. This tool allows you to select multiple issues and assign them as a group to a specific parent epic. **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.