How to add GitHub MCP
Connect GitHub through Durin and verify an allowed read and a denied request before rollout.
Prepare provider access
Use your registered GitHub OAuth client and exact app-origin /connections/callback. For a GitHub App, generate a client secret under General → Client secrets; the PEM private key serves app authentication. Confirm organization consent and repository access. The built-in endpoint is https://api.githubcopilot.com/mcp/x/all.
Save, review and enable
Open Admin → Connections → All providers. Save an OAuth draft, sign in, discover tools, save permission review and obtain the matching deployed validator. Run an approved read test, review billing, confirm activation and enable the reviewed tool.
Discovery includes all available toolsets but does not grant execution access; enable only reviewed tools.
Complete personal provider access, copy your Durin connection URL and authenticate your MCP client for that exact URL. Keep credentials and endpoint secrets out of shared evidence.
Use an approved repository
Read README.md from one approved test repository. Use the discovered read tool and its reviewed schema to enter repository and file arguments. Exclude a second test repository in Durin policy.
- Expected success: the permitted README content; activity records allow and a successful execution outcome.
- Expected denial: change only the repository to the excluded test repository; no new provider dispatch. Restore the baseline after testing.
Troubleshooting
Sign-in succeeds but the tool is unavailable
Check personal consent, team access, permitted resources, deployed validator and activation. Discovery and an approved request alone do not grant access.
Frequently asked questions
What should I record?
Record client, version, UTC date, tool/schema revision and both activity IDs when you complete the workflow.