Description
Running into an issue with the MCP server and OAuth 2.0 3LO apps.
The MCP handshake succeeds, I am able to get a session ID and tools/list returns correctly. However every tool call responds with:
{"error": true, "message": "We are having trouble completing this action. Please try again shortly."}
^ this is the response from the atlassianUserInfo tool.
The same OAuth 2.0 3LO token works fine against Atlassian REST APIs directly (api.atlassian.com/me), confirming the token and scopes are valid.
My use case
We are using flowise to help us create a chatbot and want the chatbot to talk to jira / confluence. We are using oauth 2.0 to get a user access token on the website, then we are passing the user access token to flowise to call the atlassian mcp.
Request
Please add support for OAuth 2.0 3LO tokens in the MCP server, or provide clear documentation and tooling to help developers migrate existing 3LO apps to a supported auth method.
