/
AI Capabilities with MCP for easeRequirements (Beta)

CLOUD | DATA CENTER AND SERVER

AI Capabilities with MCP for easeRequirements (Beta)

Overview

The easeRequirements MCP Server exposes a set of tools that let AI agents interact with easeRequirements (R4J) hierarchy structures directly within Jira Cloud. Using the Model Context Protocol (MCP), AI clients can navigate requirement trees, reorganize hierarchies, search issues using JQL, manage Jira issue links, and parse external documents - all on behalf of an authenticated Atlassian user.

The MCP Server connects to your Jira Cloud site via Atlassian OAuth 2.0 (3LO). All tool executions run under the authenticated user's identity, meaning Jira permissions and easeRequirements license checks apply to every operation.

The server currently supports the following categories of operations:

  • Site setup - Connect and select the target Jira Cloud site.

  • Tree navigation & search - Browse and query easeRequirements hierarchies.

  • Tree management - Create issues in batches and add, move, or remove issues in the tree.

  • Jira Links & Settings - Manage issue links and retrieve folder configuration.

  • Baselines - create, browse, and compare snapshots.

  • Coverage Views - create, copy, browse, and edit coverage views.

  • Document parsing - parse external documents and either create Jira issues directly in a Jira project or export them to an Excel file.

The functionality given by the easeRequirements MCP Server is currently available for all valid customers of easeRequirements as a beta program. Depending on further decision this may be modified or restricted in the future.

Prerequisites

Before connecting your AI client to the easeRequirements MCP Server, ensure the following:

Supported MCP Tools

The easeRequirements MCP Server provides a comprehensive set of tools that allow AI agents to interact with your requirements and Jira data - from browsing and searching hierarchies to reorganizing trees and managing issue links.

All tools execute on behalf of the authenticated user, meaning Jira permissions and easeRequirements license checks apply to every operation.

Connecting to Your Jira Site

Before using any other tool, the agent identifies and selects the target Jira Cloud site. Two tools support this:

  1. List connected sites - retrieves all Jira Cloud sites linked to the account.

  2. Select a site - sets the target site for all subsequent operations in the session.

The active site can be switched at any point during the session by selecting a different site.

Browsing & Searching Requirements

Once a Jira site is selected, the agent can navigate and query easeRequirements hierarchy structures across projects. The following tools support this:

  • List activated projects - retrieves all Jira projects where easeRequirements hierarchy is enabled

  • Get project tree - retrieves a paginated view of the full requirements tree for a project

  • Get children of a parent item - returns direct children of a specific item in the tree

  • Find projects containing an issue - identifies which easeRequirements projects contain a specific Jira issue

  • Search by JQL - searches issues within easeRequirements hierarchies using JQL

Organizing Your Requirements Tree

The agent can create Jira issues in batches and add, move, and remove issues from easeRequirements hierarchies. For destructive operations, the agent is instructed to present a summary of affected items and request explicit confirmation before proceeding.

  • Create issues in batches - creates multiple Jira issues in a single request.

  • Add issues to the tree - adds existing Jira issues as children to a parent item in the tree.

  • Move issues in the tree - moves issues to a new parent within the same or another project tree.

  • Delete issues - removes issues from the easeRequirements hierarchy.

  • Confirm operation - executes a staged operation after explicit confirmation.

Jira Links & Settings

The agent can manage Jira issue links and retrieve easeRequirements configuration for the selected site.

  • List link types - retrieves all available Jira link types (e.g., blocks, relates to).

  • Link or unlink issues - creates or removes a directional link between two Jira issues.

  • Create issue link - creates a directional link between two Jira issues.

  • Get folder issue type - retrieves the Jira issue type configured for folders in easeRequirements.

Working with Baselines

The agent can create and browse easeRequirements baselines and identify changes by comparing two baselines or a baseline with the current state of the requirements.

  • Create a baseline - creates a snapshot of the entire requirements tree, selected subtrees, or a filtered set of requirements.

  • Browse baselines - retrieves and searches existing baselines.

  • Compare baselines - identifies added, removed, and modified items by comparing two baselines or a baseline with the current state.

Working with Coverage Views

The agent can help you create and configure easeRequirements Coverage Views using natural language. It can also copy an existing Coverage View to another project or even another Jira site, and modify its structure by adding, editing, or removing columns, including columns in the middle of the view.

  • Browse Coverage Views - retrieves available views and their configurations.

  • Create a Coverage View - creates a new view with the required data sources, relationships, and columns.

  • Copy a Coverage View - creates a new view based on the configuration of an existing one from another project or even another Jira site.

  • Modify a newly created or existing Coverage View - adds, edits, or removes columns and allows the view to be renamed or made public or private.

Document Parsing

The agent can parse external documents and convert their content and hierarchy into structured Jira issues. The result can either be created directly in a Jira project or exported to an Excel file for review and import.

  1. Parse a document to Excel - converts the document into a structured Excel file formatted for Jira issue import via the [Microsoft Excel Add-in](Microsoft Excel Add-in

  2. Create Jira issues from a document - creates folders and Jira issues directly in the selected project while preserving the document structure and content.

 The agent preserves supported document elements such as headings, descriptions, tables, lists, links, and text formatting. Content that cannot be represented correctly, such as images, charts, and diagrams, is reported separately for user review.

Supported AI Clients

The easeRequirements MCP Server can be installed and used with the following AI clients.

Known Limitations

  • If the client/chat window returns an authentication error (403) try to close the dialog and retry, may wait some minutes. In case of a valid authentication in the agent, the connection should recover.

Use Cases Examples

The easeRequirements MCP Server is more than a collection of individual tools. By combining tools in sequence, an AI agent can carry out complex, multi-step requirements engineering workflows entirely through natural language - tasks that would otherwise require navigating multiple screens, manually updating spreadsheets, or cross-referencing requirements across projects.

The following use cases illustrate what becomes possible when tools work together.

Use Case I - Your personal assistant for Building and Restructuring a Requirements Hierarchy

Teams working on complex products need to organize their requirements into a structured hierarchy that reflects the system architecture - grouping them by component, system level, or development phase. This structure is not just a convenience; for many teams it is a mandatory artifact that must be maintained, reviewed, and kept in sync as the product evolves.

Challenge: Even with easeRequirements, making large-scale changes to the tree - moving many issues at once, reorganizing across components, or handling cross-project scenarios - still requires significant manual effort inside the UI.

How the MCP Server helps: The agent acts as a personal assistant for tree management. Instead of navigating screens manually, the engineer describes what needs to change in plain language - and the agent takes care of the rest, making the necessary changes across the tree while the engineer reviews and confirms.

Prompt example: “In project Z, please move all requirements from folder X to folder Y”

Use Case II - Your personal analyst for Requirements Coverage and Gap Resolution

Teams working on large projects constantly need to understand the state of their requirements - where a specific requirement lives, what depends on it, whether everything is covered, and what would be affected if something changes. Getting these answers, and then acting on the gaps, means running multiple queries, cross-referencing results across projects, and making changes manually - one by one.

Challenge: easeRequirements provides powerful search and tree navigation. But identifying coverage gaps - requirements that are not linked to any test, design, or downstream item - understanding the full impact of a change, and then acting on those gaps still requires significant manual effort across a large project.

How the MCP Server helps: The requirements engineer asks what they need to know in their own words - for example, "which requirements in folder X are not covered by test cases?" or "what would be affected if this requirement changes?" The agent runs the necessary queries, combines the results, and helps interpret what they mean. And once the gaps are identified, the engineer can instruct the agent to act on them directly - the agent adds the missing links and places issues in the right part of the tree, all within the same conversation. The agent can also help create and configure a Coverage View for ongoing coverage analysis. It can build a new view or copy and adapt an existing one from another project or Jira site. The resulting coverage table can then be reviewed in easeRequirements in the browser.

Prompt examples:

  1. “Which requirements missing verification links in folder Y, project X?”

  2. “Copy the Requirements Coverage View from project X to project Y and add a Test Execution column after the Test Cases column.”

Use Case III - Your personal housekeeper for Bulk Tree Cleanup

Over time, large projects accumulate issues that affect the quality of the requirements tree - duplicates, orphaned requirements with no parent or links, outdated issues left behind after restructuring, or requirements that were never properly placed.

Challenge: Identifying these problems manually means running multiple queries, cross-referencing results, and then deciding what to do with each finding one by one, across potentially hundreds of issues.

How the MCP Server helps: The requirements engineer asks the agent to analyze the tree - for example, "find all requirements with no links" or "are there any duplicates in this project?". The agent runs the necessary queries, surfaces the findings, and generates a quality report. Based on the results, the engineer can then ask the agent to clean up - removing or reorganizing the identified issues - with confirmation required before any changes are made.

Before making bulk changes, the engineer can ask the agent to create a baseline of the relevant requirements. After the cleanup, the agent can compare that baseline with the current state and show exactly what was added, removed, or modified.

Prompt examples:

  1. “Please scan project X tree, can you find duplicated requirements?”

  2. “Create a baseline of project X before the cleanup, then compare it with the current state after the changes.”

Use Case IV - Your personal document-to-requirements converter

Requirements are often received in external documents with different structures, formatting, and levels of detail. Turning these documents into a consistent requirements hierarchy manually can be time-consuming and error-prone.

Challenge: The document structure, requirements, descriptions, tables, lists, and links must be identified and transferred without losing content or placing items incorrectly in the hierarchy.

How the MCP Server helps: The requirements engineer provides a document, and the agent converts its content and hierarchy into a structured Excel file. The file can be reviewed and adjusted before the resulting folders and Jira issues are imported using the dedicated [Microsoft Excel Add-in](Microsoft Excel Add-in Alternatively, the agent can create the resulting hierarchy directly in a selected Jira project.

Prompt example: “Parse this document and export the resulting requirements hierarchy to an Excel file ready for Jira import.”

Getting Access

The easeRequirements MCP Server is currently available to beta customers. To get access, contact support.easesolutions.com and you will be provided with the MCP Server URL and onboarding instructions.