Skip to content

Copilot cloud agent: connect to the Atlassian MCP server directly over HTTP - #46358

Open
playb0t wants to merge 1 commit into
github:mainfrom
playb0t:atlassian-mcp-native-http
Open

Copilot cloud agent: connect to the Atlassian MCP server directly over HTTP#46358
playb0t wants to merge 1 commit into
github:mainfrom
playb0t:atlassian-mcp-native-http

Conversation

@playb0t

@playb0t playb0t commented Oct 17, 2026 •
edited
Loading

Copy link
Copy Markdown

Why:

Closes: #46357

The Atlassian example launches a local npx mcp-remote@latest bridge 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):

  • Use type: "http", url and headers instead of a local npm bridge.
  • Read the complete Authorization value from $COPILOT_MCP_ATLASSIAN_AUTH. The secret contains Basic followed by a space and base64-encoded email:api_token, so the example does not depend on interpolation within a header string or on the transport adding a scheme.
  • Keep Atlassian's recommended v2 endpoint and note that v1/mcp remains supported.

The changed example parses as JSON and passes the scoped content-linter.

Check off the following:

  • A subject matter expert (SME) has reviewed the technical accuracy of the content in this PR. In most cases, the author can be the SME. Open source contributions may require an SME review from GitHub staff.
  • The changes in this PR meet the docs fundamentals that are required for all content.
  • All CI checks are passing and the changes look good in the review environment.

@github-actions github-actions Bot added the triage Do not begin working on this issue until triaged by the team label Oct 17, 2026
@github-actions

github-actions Bot commented Oct 17, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

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 links

Note: Please update the URL for your staging server or codespace.

The table shows the files in the content directory that were changed in this pull request. This helps you review your changes on a staging server. Changes to the data directory are not included in this table.

Source Review Production What Changed
copilot/how-tos/copilot-on-github/customize-copilot/configure-mcp-servers.md fpt
ghec
 fpt
ghec

Key: fpt: Free, Pro, Team; ghec: GitHub Enterprise Cloud; ghes: GitHub Enterprise Server

🤖 This comment is automatically generated.

@lecoursen

lecoursen commented Oct 19, 2026

Copy link
Copy Markdown
Member

Thanks for raising an issue, @playb0t! We’ll get this triaged for review by the appropriate team.

@github github deleted a comment Oct 22, 2026
@subatoi subatoi removed the triage Do not begin working on this issue until triaged by the team label Oct 22, 2026
notcalambur

This comment was marked as off-topic.

Sign in to view

@playb0t
Copilot cloud agent: connect to the Atlassian MCP server directly ove…
9007f44 
…r HTTP

Signed-off-by: Alex Gercog <186247040+playb0t@users.noreply.github.com>
@playb0t
playb0t force-pushed the atlassian-mcp-native-http branch from 758d232 to 9007f44 Compare November 3, 2026 10:02
@playb0t

playb0t commented Nov 3, 2026

Copy link
Copy Markdown
Author

The example now uses "Authorization": "$COPILOT_MCP_ATLASSIAN_AUTH", with the complete Basic <base64(email:api_token)> value stored in the secret. GitHub's remote MCP configuration documentation explicitly supports a whole-value secret reference for headers, and Atlassian documents the complete Basic header value. This avoids relying on substitution inside a prefixed string or on Copilot adding the scheme. I checked the documented configuration contract; I have not run this configuration inside Copilot cloud agent. The updated JSON example and scoped content-linter both pass.

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.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

1 more reviewer
@notcalambur notcalambur notcalambur left review comments
Reviewers whose approvals may not affect merge requirements

At least 1 approving review is required to merge this pull request.

Assignees

No one assigned

Labels

builder persona

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

Copilot cloud agent: the Atlassian MCP example uses a local npm bridge for a remote server

4 participants

@playb0t @lecoursen @notcalambur @subatoi