MCP Server to fetch ticket items for code review in external AI tool

[Pablo Adames]

We use VSCode and Warp-AI as coding IDEs and their integrated AI models through paid plans. We also have JIRA and Confluence Cloud Company accounts.

Can we use the Atlassian Rovo MCP Server from our IDEs to search ticket content, given the JIRA ticket name alone?
Our goal is to expedite code reviews. Every human reviewer should be able to specify what records from the ticket they want/need retrieved to start the code review, using the AI model of their preference/budget and the goals of the review. Not all reviews are the same. Sometimes you may want to search for related tickets, and sometimes you want to scope the review exclusively to the given ticket.

Thanks,
Pablo

[Tomislav Tobijas · Accepted solution]

Hi @Pablo Adames ,

I know that Rovo Dev is available in VS Code > see February announcement here: Rovo Dev is now generally available in VS Code 

As for the MCP server itself, it's stated here that VS Code is a supported IDE. Warp-AI is not explicitly listed as a natively supported client, but MCP should be able to connect via "mcp-remote" proxy.

I'm not strictly a dev myself, so I don't work in VS Code that often, but based on what I've seen, once you configure the MCP server, you should be able to use natural language prompts within your IDE AI chat to have things like:

• Rovo search - search for work items
• Rovo fetch - e.g., fetch description of the specific work item

More on that here: Using Rovo search and fetch in the Atlassian Rovo MCP Server 📚

Btw, I'm going to move this to the Rovo forum group for someone to maybe chime in if they have more info.
Apart from that, you could check the following discussion group for any additional info on this topic: Atlassian Rovo MCP Server 

Cheers,
Tobi

[Pablo Adames]

In Warp-AI, you will have to create a one-time OAuth server configuration for the Rovo MCP server with:

mnpx mcp-remote https://mcp.atlassian.com/v1/mcp

This will open an authorization page on your default browser with Atlasian.

After this, the workflow that looks more ergonomic to me is:

Use a 3-step prompt sequence:
1. Resolve the ticket from the title
“Search Jira for ticket named <title> in project <PROJ> and return the best match + 2 alternatives.”
2. Fetch review context
“Fetch <KEY> description, acceptance criteria, linked tickets, related Confluence pages, and unresolved comments.”
3. Diff-vs-requirements check
“Compare current git diff/PR against that ticket context and output: missing requirements, risky changes, and test gaps.”

Item #3 is whatever your code reviews call for, really!

[Pablo Adames]

In Warp, the Oz agent realizes you have authorized a remote MCP server for Atlasian (in my case), and it goes on to search for the JIRA tickets. It gives a list of the top 5 closest matches.  
If there is an exact match, you will get it up top and with a message like:

Exact Jira match found:

• Issue key: IVAS-2791
• Summary: web: Harden Thermal Modal numeric validation for HVR-side thermal-processing settings
• Project: IVT Video Analytic System
• Status: In Review
• Assignee: Pablo Adames
• URL: https://my-company.atlassian.net/browse/IVAS-2791

[Pablo Adames]

My only comment is that at the current cost of the Warp to Rovo MCP bridge, a simple fetch can cost me 10 to 20 credits and a few seconds to complete, up to a minute.

At this price point, I would not use this mechanism for code reviews; we do tens of them a day. I would leave it for real investigations on our large ticketing and internal article knowledge base for code words.

If it were faster and cheaper, say a credit or two, then I would promote it as a code-review workflow. For now, we will continue to copy and paste from the ticket to the prompt.   

[Tomislav Tobijas]

Thanks for sharing these detailed steps and analysis @Pablo Adames 🙌

Much appreciated!!

As for the actual cost... yeah - I see a lot of people still exploring Rovo usage and how to optimize it. 
Related to that, you could probably share feedback directly from Rovo UI/Chat (not sure if there's something like that for the MCP server).