Sean Bourke Atlassian Team

Comments

  • Hey @Faisal Hasan This is a common use case which we see often - we absolutely support MCP Gateways. The key is determining the approach you want to use for auth - using passthrough OAuth (or XAA) will ensure that permissions and actions always align to the user's existing permissions and are attributable. Our newer v2…
    in Do Atlassian allow customers’ MCP Gateways to connect to Atlassian Cloud MCP Server Comment by Sean Bourke September 3
  • A huge thank you to everyone who tested and provided feedback throughout the v2 preview, your support helped us to improve the Atlassian MCP in readiness for v2. I'm happy to share that Atlassian Rovo MCP v2 is now available via `https://mcp.atlassian.com/v2/mcp`. This introduces broader support for Loom, Goals, Projects,…
    in [Preview] Atlassian Rovo MCP v2 Comment by Sean Bourke September 1
  • Hey @unsafe9 Wanting to provide an update here - we understand that some customers may be utilising other approaches to exposing our MCP server such as MCP Gateways and require access to all tools proactively, where the discover/execute model will not suffice. We are working on an optional override which you'll be able to…
    in [Preview] Atlassian Rovo MCP v2 Comment by Sean Bourke July 30
  • Hey @Yatish Madhav Given this is a preview of the future of our MCP server, it would be appropriate to use this for testing purposes today. This means: * You'll be able to provide real feedback before it moves to GA and help us understand where we can improve. * You'll be ready to adopt it day 1.
    in [Preview] Atlassian Rovo MCP v2 Comment by Sean Bourke July 30
  • Hey @Leon Remennik Thanks for flagging this - there may be some associated to a client or session cache resulting in this. Could you please try logging out / logging back in and trying again? We're going to look into this from our end as well.
    in [Preview] Atlassian Rovo MCP v2 Comment by Sean Bourke July 24
  • Hey @Rebekka Heilmann _viadee_ Thanks for flagging this. The v2 of Atlassian Rovo MCP exposes high-level scopes which can only be used for MCP interactions - this means that the same bearer token couldn't be utilised for interactions with generic APIs. These scopes are not yet available in the Service Account Token…
    in [Preview] Atlassian Rovo MCP v2 Comment by Sean Bourke July 14
  • Hey @unsafe9 Thanks for the feedback and appreciate the perspective of some MCP clients providing tool-name level search to support tool discovery without loading full tool context. The upcoming MCP release candidate implements SEP-2549 which brings us improved controls related to per-user tool caching (i.e. controlling…
    in [Preview] Atlassian Rovo MCP v2 Comment by Sean Bourke July 3
  • @Nicola Pacini thanks for the clarification. If you still have the v1 tools declared, you're likely to run into conflicts where it will refer to those tools instead - for example, it may request `createConfluenceContent` on the older v1 version rather than the new one which supports databases and whiteboards. The most…
    in [Preview] Atlassian Rovo MCP v2 Comment by Sean Bourke July 2
  • Thanks everyone for the questions and feedback. I've responded to each of the questions in this comment. @Michael Branders while this is an early release, we believe this approach will unlock the ability to deliver more tools for more products. We're exploring bringing Bitbucket into the folk; but there are a few things…
    in [Preview] Atlassian Rovo MCP v2 Comment by Sean Bourke July 2
Avatar