CLOUD | DATA CENTER AND SERVER
Connect Atlassian Rovo with easeRequirements MCP Server and Assign it to an Agent
This guide explains how to add the easeRequirements custom Model Context Protocol (MCP) Server as a tool in Atlassian Rovo and then assign it to a Rovo agent. It includes prerequisites, authentication flow notes, and step‑by‑step setup. For some operations Jira admin permissions necessary.
Overview
The easeRequirements MCP Server exposes tools that let AI agents perform tree operations, create/search requirements, and analyze traceability within Jira projects that use easeRequirements. Rovo integrates external MCP servers via OAuth-based dynamic discovery, enabling agents to call these tools securely on behalf of authenticated Atlassian users.
Within Atlassian Rovo an MCP server can only be used by an agent, not in the regular Rovo command window.
Prerequisites
Jira Cloud site with Atlassian Intelligence and Rovo enabled for the organization (see https://www.atlassian.com/software/rovo/guides/admin-guide/rovo-activation#confirm-activation).
easeRequirements app installed and licensed in the target Jira Cloud site.
easeRequirements MCP Server:
https://mcp.easesolutions.com/mcpAtlassian login with access to the target Jira site.
Administrator or agent configuration permissions in Rovo.
About authentication: The easeRequirements MCP Server implements an OAuth-aware proxy. When Rovo connects, users authenticate via Atlassian OAuth 2.0 (3LO). Access tokens are issued by Atlassian (with automatic refresh) and validated by the MCP proxy for each tool invocation.
Step 1 - Activate and access Rovo
Ensure Atlassian Intelligence is enabled in Admin Hub and that Rovo features (Chat, Search, Agents) are set to On.
Open Jira. In the top navigation, click Ask Rovo, then open the Rovo menu and select Browse agents.
Step 2 - Connect easeRequirements MCP Server to the Organization (Admin setup)
To connect easeRequirements MCP Server to your organization, you can follow Atlassian’s documentation: https://support.atlassian.com/organization-administration/docs/add-an-external-mcp-server-from-atlassian-administration/
easeRequirements MCP Server: https://mcp.easesolutions.com/mcp
Step 3 - Create or open your Rovo agent
Create a new agent or open an existing one that will use easeRequirements tools.
E.g. Click ROVO button in Jira → Select Create Agent → Select Agent to start from scratch. Then ROVO Studio startsGo to Agent Details
Update the Instructions field with:
You are a Requirements and Jira Management assistant. Jira site handling for easeRequirements MCP: 1. The MCP server already keeps a site selected and persists it server-side. Treat the site as established and call the requested working tool directly (e.g. get_activated_projects, get_project_tree). 2. Reserve select_jira_site for a single case: if a tool reports that no site is selected, select the site once and continue. One selection covers the rest of the conversation. Project handling: 1. Work in the project the user references or is currently working in. 2. When the project is unclear, ask the user which project to use. Root-level parent key: When moving or adding issues to the tree root, pass -1 (plain integer, no quotes) as the map key in parents. Example: {-1=[{childId=TP-23}]}. Do NOT pass "-1" (quoted string) — the server will not recognise it.Click on “Add tools”.
Scroll to the bottom in the left-side panel, and select the easeRequirements MCP Server.
You will see the list of tools available for the MCP Server, click on “Add all existing and future easeRequirements MCP tools”, or enable part of the tools you are interested in using.Click on “Add”.
Step 4 - Publish and test
Click Publish to activate the agent with connected tools.
The agent should now be accessible through “Ask Rovo” → “Browse Agents”.
“Fetch easeRequirements folder issue type.”
“Create quality report for requirements under folder X in project Y”
“Create a folder named ‘Functional Requirements’ under folder ‘Requirements’.”
Understanding the authentication flow
Dynamic client registration: Rovo requests temporary client registration from the MCP proxy; no manual OAuth client setup needed by the admin.
User login: The proxy builds an Atlassian OAuth request and opens the browser to auth.atlassian.com.
Token handling: Access token (1 hour) + refresh token are managed through the MCP proxy and attached to subsequent tool calls as Authorization: Bearer <token>.
Auto-refresh: When access tokens expire, Rovo refreshes through the proxy; no user action required until consent changes or is revoked.
Security and permissions
All tool executions run under the authenticated user’s Atlassian identity; Jira permissions and easeRequirements license checks apply.
The MCP proxy validates tokens and rejects unauthorized requests (401/403).