Cursor successfully invokes the Atlassian MCP server, but results are not making it back to the agent/UI

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Cursor’s agent-facing MCP calls to the configured Atlassian MCP server fail with the generic message “We are having trouble completing this action. Please try again shortly.”, even though the Atlassian MCP server itself successfully executes the same tool calls.

This appears to be a Cursor-side MCP result propagation or translation issue between the MCP server response and the agent/UI layer, not an Atlassian auth or Confluence access issue.

Environment
Cursor on Windows
Atlassian MCP server configured globally in mcp.json
Config:
{
“mcpServers”: {
“Atlassian-MCP-Server”: {
“url”: “https://mcp.atlassian.com/v1/mcp
}
}
}

Evidence
Atlassian MCP server is working
From \AppData\Roaming\Cursor\logs\20260407T111001\window1\exthost\anysphere.cursor-mcp\MCP user-Atlassian-MCP-Server.log

OAuth/connect succeeded:

MCP OAuth tokens persisted
OAuth tokens saved
Successfully connected to streamableHttp server
Tool calls succeeded:

Successfully called tool ‘getAccessibleAtlassianResources’
Successfully called tool ‘atlassianUserInfo’
Successfully called tool ‘getConfluenceSpaces’
Cursor MCP layer sees the tool calls
From \AppData\Roaming\Cursor\logs\20260407T111001\window1\workbench.mcp.allowlist.log

Cursor receives the tool invocations, for example:
mcpToolCall bubble: serverName=“Atlassian-MCP-Server”, toolName=“getConfluenceSpaces”
The calls are allowlisted:
shouldBlockMcp: ALLOWED (explicitly in allowlist) toolName=“getConfluenceSpaces”
UI/agent side still fails
From \AppData\Roaming\Cursor\logs\20260407T111001\window1\renderer.log

Nearby generic error:
An unknown error occurred. Please consult the log for more details. {}
The exact text We are having trouble completing this action was surfaced to the agent, but I did not find that exact string persisted in the local log files.

Request ID: 4e17cd28-8984-4605-894e-85c604a7eb87

Steps to Reproduce

Configure Atlassian MCP server in Cursor.
Ensure OAuth/login completes.
Run an MCP tool from the agent, for example:
getAccessibleAtlassianResources
getConfluenceSpaces with cloudId set
Observe that the agent receives:
“We are having trouble completing this action. Please try again shortly.”

Expected Behavior

The MCP tool result should be returned to the agent.

Operating System

Windows 10/11

Version Information

Version: 3.0.12 (user setup)
VSCode Version: 1.105.1
Commit: a80ff7dfcaa45d7750f6e30be457261379c29b00
Date: 2026-04-04T00:13:18.452Z
Layout: editor
Build Type: Stable
Release Track: Default
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
OS: Windows_NT x64 10.0.26100

For AI issues: which model did you use?

gpt-5.4-medium

Does this stop you from using Cursor

No - Cursor works, but with this issue

Hi @VsevolodK!

The message We are having trouble completing this action. Please try again shortly. is returned by Atlassian, and historically has signaled a reliability issue on the Atlassian side!

So far, I have not been able to reproduce when using Windows/Cursor 3.0.12/the Atlassian MCP server, making the same tool calls.

  1. Is getConfluenceSpaces the only tool not working correctly?
  2. Could you try clearing your MCP tokens and re-authenticating?
    a. Open the command palette with Cmd + Shift + P
    b. “Clear all MCP tokens”
    c. Re-authenticate with the Atlassian MCP server

This will force a fresh auth session and may resolve the issue if it’s related to a stale token.