Githubcopilot: MCP server, CLI and agent surfaces

Sign-in required, tools not seen, not counted. The MCP endpoint listed for Githubcopilot at api.githubcopilot.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in.

Fact sheet

Company	Githubcopilot (registry title: GitHub)
Domain	githubcopilot.com
Category	Developer Tools (Ora leaderboard category)
MCP server	Sign-in required (OAuth without client registration)
Tranco rank	3,131 on the list of 4 November 2026
Ora score	none: Ora returned no cached score for githubcopilot.com when asked on 5 November 2026
Company found through	the awesome-remote-mcp-servers list; the GitHub MCP Registry
Last verified	4 November 2026

MCP server

Endpoint	`https://api.githubcopilot.com/mcp`
How it was found	listed in the awesome-remote-mcp-servers list; the GitHub MCP Registry
Transport	streamable-http
HTTP status	401
Connected	4 November 2026, 20:01 UTC
Handshake time	1,246 ms over 1 attempt

The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools.

Connector log

2 connections on 4 November 2026, read-only methods only

19:56:02Z https://api.githubcopilot.com/mcp sent initialize result auth-required (HTTP 401) 1320 ms
20:01:37Z https://api.githubcopilot.com/mcp sent initialize result auth-required (HTTP 401) 1246 ms

Authentication

Auth type	OAuth without client registration
What the challenge said	`Bearer error="invalid_request", error_description="No access token was provided in this request", resource_metadata="https://api.githubcopilot.com/.well-known/oauth-protected-resource/mcp"`
Protected resource metadata	api.githubcopilot.com
Authorization server metadata	github.com
Auth as listed by a registry	OAuth2.1 (a claim, not checked by connecting)

The sign-in route, step by step

Request https://api.githubcopilot.com/mcp without a token. It answers 401 and a WWW-Authenticate header.
Read the OAuth metadata at https://github.com/.well-known/oauth-authorization-server/login/oauth. It lists no registration endpoint.
Register the client by hand in the company's developer settings, or present a client ID metadata document if the authorization server supports one.
Authorize as a person, then retry the endpoint with the bearer token. The connector stops after step 2.

See OAuth for MCP: client ID metadata documents and dynamic registration for how each route works.

CLI

No CLI is on record for Githubcopilot. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See shipping a CLI agents can use.

Other agent surfaces

Agent surfaces other than MCP and CLI
Surface	Result
OpenAPI file	The request failed.
WebMCP in the initial HTML	Not checked: the home page was not read by the shared crawl.
MCP discovery file	Not read: robots.txt or the crawl budget kept the shared crawl away from this path.
A2A agent card	Not read: robots.txt or the crawl budget kept the shared crawl away from this path.
A2A agent card (older path)	Not read: robots.txt or the crawl budget kept the shared crawl away from this path.
agents.json	Not read: robots.txt or the crawl budget kept the shared crawl away from this path.
OAuth authorization server metadata	Not read: robots.txt or the crawl budget kept the shared crawl away from this path.
NLWeb endpoint	Not checked in this edition.

Registry listings

Registry listings
Registry	Listed
Official MCP Registry	No
GitHub MCP Registry	Yes
awesome-remote-mcp-servers	Yes
Smithery	Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026.
Glama	Not checked: Glama's API needs a key and attribution terms.