Atlassian MCP integration with Claude.ai returns stale cached Jira ticket content

[David Sanchez]

Description

I am using the Atlassian MCP (Model Context Protocol) integration with Claude.ai and have encountered an issue where the content returned for Jira tickets does not match the current live version visible directly in Jira.

Integration details:

• Tool: Fetch content with ARI (beta) from Atlassian

• Accessed via: Claude.ai (Anthropic)

• Project affected: Jira (cloud)

Issue description: When Claude fetches a Jira ticket using the Atlassian MCP integration, the content returned (description, acceptance criteria, comments) appears to be served from a cache rather than fetched live from Jira. The returned content is days outdated — it does not reflect recent edits, added acceptance criteria, or comments that are clearly visible when opening the same ticket directly in Jira.

Steps to reproduce:

1. Connect the Atlassian MCP integration in Claude.ai

2. Ask Claude to fetch a Jira ticket by its key (e.g. LP2-17)

3. Compare the content returned by Claude with the same ticket opened directly in Jira

Expected behaviour: The integration returns the current live version of the ticket, matching what is visible in Jira.

Actual behaviour: The integration returns a version of the ticket that is several days outdated and does not reflect recent changes made to the ticket.

Additional question: Is there a way to force a cache refresh or bypass the cache when fetching content via the MCP integration?

URL: inspireai.atlassian.net

[Arkadiusz Wroblewski]

Welcome to the Community, @David Sanchez !

Sorry for late Answer.

We should probably figure out whether Claude is just clinging to old conversation context or if the Atlassian MCP tool is actually pulling stale data from Jira. As far as I know, there isn't a native "force refresh" or "bypass cache" command for the Rovo MCP server just yet.

To rule out Claude's memory, please start a completely fresh chat session and ask it to pull the issue again, but explicitly tell it to include the "last updated" and "latest comment" timestamps in its response. If it’s still serving up old data, try disconnecting and reconnecting your Atlassian integration to force a fresh authentication sync, and double-check that you're logged into the exact same account on both ends.

Best,

Arkadiusz☀️