VS Code’s Local GitHub Copilot harness supports the illustrated OAuth connection flow, including sign-in, consent, tool discovery and a connected-account check. Broader content workflows and other clients require separate verification. Follow your client’s own configuration documentation and check whether it can use the plugin’s connection contract.
Required client capabilities
-
Remote Streamable HTTP with JSON responses.
-
Caller authentication headers supported by the client, with credentials stored privately.
-
A protocol version supported by the plugin.
The app offers remote Streamable HTTP and OAuth discovery for administrator-registered clients. Clients must support PKCE and a preconfigured client ID; automatic dynamic client registration is unavailable. The app does not provide a local process or the older standalone HTTP+SSE transport. Use the Local harness for the documented VS Code flow; the separate Copilot SDK harness did not expose the Confluence tool in our checks. Matching protocol requirements alone does not establish that a particular client version works end to end.
Shared endpoint and token settings are in Connect your MCP client. Deployment scope is in Compatibility and limitations.