github.com
GitHub is a code hosting and developer collaboration platform with repositories, pull requests, issues, automation, and AI-assisted development features. It provides APIs and tooling for automating repository, workflow, app, and account-related tasks.
GitHub exposes a public docs HTTP API, authenticated REST and GraphQL APIs on api.github.com, a remote MCP server on api.githubcopilot.com/mcp/, and the authenticated `gh` CLI.
- GitHub MCP Serverdetected
- GitHub REST APIdiscovered
- GitHub Docs APIsdiscovered
- GitHub GraphQL APIdiscovered
- GitHub CLIdiscovered
Create a personal access token from your GitHub account settings using Managing your personal access tokens. Choose scopes or fine-grained permissions based on the API or MCP actions you need. GitHub's docs note that fine-grained PATs include read access to public repositories, while classic PATs need scopes such as public_repo for public-repo access.
Register a GitHub App using Register a GitHub App. After registration, generate the app's private key and use GitHub's app-auth flows to mint the token needed for your use case: an installation access token for app installations or a user access token when acting on behalf of a user, as described under Authenticate as an installation and Authenticate on behalf of users.
Create an OAuth app using Creating an OAuth app. Configure its callback URL, then send users through GitHub's OAuth authorization flow as documented in Authorizing OAuth apps to obtain a user access token with the scopes your integration needs.
$ gh auth loginAcquired by the CLI — running gh auth login opens the auth flow and stores the credential.
For the remote GitHub MCP server at https://api.githubcopilot.com/mcp/, compatible MCP hosts can use one-click OAuth sign-in. GitHub's MCP docs say you do not need to create a PAT for this path: configure the server URL in your MCP host or IDE and approve access in the browser when prompted. See Setting up the GitHub MCP Server and the GitHub MCP Server README.
conventions · 1/8 published
- integrations.json✗
/.well-known/integrations.json - llms.txt✓https://github.com/llms.txt
- API catalog✗
/.well-known/api-catalog - OpenAPI document✗
/api/schema/, /openapi.json, /swagger.json, /api/openapi.json, or /v1/openapi.json - MCP server card✗
/.well-known/mcp/server-card.json - OAuth protected resource✗
/.well-known/oauth-protected-resource - Agent card✗
/.well-known/agent-card.json - Agent skills✗
/.well-known/agent-skills/index.json
Publish these signals → /publishing