Target 1 → C. http

Target 2 → A. Bearer

The completed configuration is:

{

" servers " : {

" github " : {

" type " : " http " ,

" url " : " https://api.githubcopilot.com/mcp/ " ,

" requestInit " : {

" headers " : {

" Authorization " : " Bearer ${env:GITHUB_PAT} "

}

}

}

}

}

The first target must be http because the GitHub MCP endpoint is a remotely hosted MCP server accessed through an HTTPS URL. GitHub ' s MCP configuration supports remote HTTP servers using the http transport type, whereas stdio and local are intended for MCP servers launched as local processes. GitHub documentation identifies http as a valid MCP server type for remote endpoints.

The second target must be Bearer . GitHub ' s documented PAT authentication pattern places the token in the HTTP Authorization header in the form Bearer < PAT > . Therefore, the expression combining Bearer with ${env:GITHUB_PAT} supplies the credential in the expected authentication scheme without embedding the token directly in the committed workspace configuration. GitHub ' s MCP setup documentation explicitly demonstrates an Authorization header using Bearer YOUR_GITHUB_PAT for the hosted GitHub MCP endpoint.

Digest, Token, and x-api-key do not match GitHub ' s prescribed PAT authentication syntax. Likewise, local and stdio would describe a locally executed MCP server rather than the specified remote endpoint.

Study Guide Reference Topics: Implement Tool Use and Environment Interaction; configure MCP servers; remote MCP transports; secure credential handling; tool authentication.