feat(integrations): add Atlassian Rovo MCP server (OAuth 2.1)#408
Merged
Conversation
Adds a catalog entry for the official Atlassian Rovo hosted MCP server. Uses shttp transport with server-managed OAuth 2.1 - no client credentials required. Covers Jira, Confluence, Bitbucket, and JSM in a single connection. Co-authored-by: openhands <openhands@all-hands.dev>
neubig
approved these changes
Jul 13, 2026
neubig
left a comment
neubig
left a comment
Member
There was a problem hiding this comment.
Assuming that this has been tested, LGTM!
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds a catalog entry for the official Atlassian Rovo hosted MCP server — Atlassian's first-party, fully managed remote MCP server that surfaces Jira, Confluence, Bitbucket, and Jira Service Management through a single connection.
What's new
integrations/catalog/atlassian-rovo.json— new catalog entryintegrations/catalog-index.js— regenerated vianpm run build:integrationsDesign decisions
This entry is deliberately separate from the existing
atlassian.json(which drives the communityuvx mcp-atlassianstdio package with manually configured API tokens). The Rovo server is a different product with a different connection model:atlassian.jsonatlassian-rovo.json(this PR)mcp-atlassianviauvx(stdio)stdioshttpWhy
clientAuthentication: "none"The Atlassian Rovo MCP server owns the entire OAuth 2.1 flow itself (identical pattern to
superhuman-mail.json). There are no client credentials to configure — the user simply authenticates through the browser prompt that the server initiates.Testing
References
https://mcp.atlassian.com/v1/mcp/authv2This PR was created by an AI agent (OpenHands) on behalf of the user.
@jpelletier1 can click here to continue refining the PR