A developer is configuring a GitHub Copilot agent to use GitHub's hosted remote MCP server so the agent can call GitHub APIs as tools. Which endpoint URL and transport type should the agent definition specify?
Select an answer to reveal the explanation.
Short Explanation
You need the hosted GitHub MCP URL and the SSE transport. stdio only works for local processes, so it won't reach remote HTTP endpoints. Match the transport to where the server lives.
Full Explanation
GitHub provides the hosted remote MCP server at https://api.github.com/mcp/v1 that exposes GitHub API capabilities (repository operations, issues, pull requests, etc.) as MCP tools. When configuring the Copilot agent to use this endpoint, two fields must be correct simultaneously: the URL and the transport.
The configuration specifying https://api.github.com/mcp/v1 with stdio is incorrect in its transport choice. stdio transport means the runtime launches local child process and communicates with it over standard input/output. Remote HTTP endpoint cannot be reached via stdio — there is no local process to spawn.
The configuration specifying https://api.github.com/mcp/v1 with sse is correct. The GitHub remote MCP server uses sse (Server-Sent Events) as its transport. SSE is an HTTP-based protocol where the server pushes events to the client over persistent connection. The agent runtime connects to https://api.github.com/mcp/v1 via SSE, completes the MCP handshake, and then can call GitHub API tools. Authentication (typically GitHub token) is passed in request headers, not in the URL or transport field.
The configuration specifying wss://copilot.github.com/mcp with websocket is incorrect because there is no WebSocket-based MCP transport in the current MCP specification, and wss://copilot.github.com/mcp is not real GitHub endpoint.
The configuration specifying https://github.com/settings/mcp with oauth is incorrect because https://github.com/settings/mcp is browser settings page, not MCP server endpoint, and oauth is authentication mechanism, not valid MCP transport type.
Critical exam point: always match transport to server location. stdio = local process; sse = remote HTTP server. Getting this wrong means the agent runtime cannot establish connection regardless of how correct the rest of the configuration is.