Repository navigation
Copilot cloud agent: connect to the Atlassian MCP server directly over HTTP - #46358
Conversation
How to review these changes 👓Thank you for your contribution. To review these changes, choose one of the following options: A Hubber will need to deploy your changes internally to review. Table of review linksNote: Please update the URL for your staging server or codespace. The table shows the files in the
Key: fpt: Free, Pro, Team; ghec: GitHub Enterprise Cloud; ghes: GitHub Enterprise Server 🤖 This comment is automatically generated. |
|
Thanks for raising an issue, @playb0t! We’ll get this triaged for review by the appropriate team. |
…r HTTP Signed-off-by: Alex Gercog <186247040+playb0t@users.noreply.github.com>
758d232 to
9007f44
Compare
|
The example now uses Atlassian announced v2 as generally available on September 8, 2026. Its current README recommends v2 for new configurations and says v1/mcp remains supported. I kept the v2 URL and added a sentence confirming v1 support. |
mchammer01
left a comment
There was a problem hiding this comment.
Thanks for fixing an outdated recommendation ✨
LGTM ![]()
There was a problem hiding this comment.
🔵 Needs a closer look
Repository evidence confirms the JSON shape and MCP substitution syntax, but verifying Atlassian v2 endpoint compatibility, Basic-auth behavior, and an end-to-end cloud-agent session requires external service or SME confirmation.
No open issues 🎉
What changed in this PR
Updates the Atlassian MCP server example to connect directly to Atlassian’s remote HTTP endpoint using a complete Basic authorization value from an Agents secret instead of a local bridge.
Changes:
- Replaces the
npx mcp-remotebridge with an HTTP MCP configuration using Atlassian’s recommended/v2/mcpendpoint. - Uses the
COPILOT_MCP_ATLASSIAN_AUTHsecret for the completeAuthorizationheader value. - Notes that the
/v1/mcpendpoint remains supported.
| File | Description |
|---|---|
| content/copilot/how-tos/copilot-on-github/customize-copilot/configure-mcp-servers.md | Updates the Atlassian MCP configuration and authentication instructions to use a direct authenticated HTTP connection. |
Review effort: Lite
|
Thanks very much for contributing! Your pull request has been merged 🎉 You should see your changes appear on the site in approximately 24 hours. If you're looking for your next contribution, check out our help wanted issues ⚡ |
Why:
Closes: #46357
The Atlassian example launches a local
npx mcp-remote@latestbridge for a remote API-token connection. GitHub documents remote HTTP MCP servers with custom headers, and Atlassian documents the direct v2 endpoint with Basic authentication.What's being changed (if available, include any code snippets, screenshots, or gifs):
type: "http",urlandheadersinstead of a local npm bridge.$COPILOT_MCP_ATLASSIAN_AUTH. The secret containsBasicfollowed by a space and base64-encodedemail:api_token, so the example does not depend on interpolation within a header string or on the transport adding a scheme.The changed example parses as JSON and passes the scoped content-linter.
Check off the following: