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

Page: /copilot/how-tos/copilot-on-github/customize-copilot/configure-mcp-servers, section "Example: Atlassian".

The example sets the Atlassian MCP server as "type": "local". It spawns npx mcp-remote@latest to reach https://mcp.atlassian.com/v1/mcp. The API token travels through env and a --header argument.

Three things point to a direct configuration instead:

• The same page documents remote servers: "type": "http" with url and headers, and $COPILOT_MCP_* substitution in string fields. The Cloudflare example on the page already uses a remote type.
• Atlassian's page on API-token authentication shows a direct url plus headers entry on https://mcp.atlassian.com/v2/mcp. It uses no bridge.
• The Atlassian server README recommends /v2/mcp for all clients while keeping the v1 endpoints supported. Every client snippet there uses v2/mcp.

Proposed change: "type": "http", "url": "https://mcp.atlassian.com/v2/mcp", and an "Authorization": "Basic $COPILOT_MCP_ATLASSIAN_API_KEY" header. The agent then talks to the server directly. No third-party package is installed at run time in the agent's environment, and the secret goes straight to the server. I have the change ready and will open a pull request against this issue.