- GitHub (GitHub MCP) — C1 connects to GitHub’s own hosted MCP server at
api.githubcopilot.comand passes each tool call through. The tools are the ones GitHub publishes, so the set follows GitHub’s own releases. - GitHub API — C1 hosts an MCP server that turns GitHub’s REST API into tools for developer workflows. C1 defines the tool set and sets default approval levels for risky actions.
Choose between the two options
Choose GitHub if you want the tool set GitHub itself publishes, including discussions, Copilot features, and package-related scopes, and you want new GitHub tools to appear as GitHub releases them. Choose GitHub API if you want a developer-workflow tool set with C1’s default approval levels already applied to risky actions. It also includes tools that GitHub’s hosted server doesn’t offer as separate tools, such as reviewing pending deployments for a workflow run and listing a pull request’s requested reviewers separately for users and teams.- GitHub MCP
- GitHub API
C1 registers as a client of GitHub’s hosted MCP server rather than translating GitHub’s API itself. Your users’ AI clients only see C1-governed MCP tools. C1 passes each tool call to With your OAuth app ready, register the server in C1.The first time a user calls a GitHub tool from their AI client, C1 redirects them to GitHub to sign in and approve the requested scopes, then returns them to C1 (authorizing OAuth apps).If your organization uses SAML single sign-on, authorize the token for it after you create it. If the organization requires approval of fine-grained tokens, an organization owner must approve the token before it can reach the organization’s resources. For a fine-grained token, the resource owner must be the organization for the token to reach its repositories. Enterprise Managed Users can’t use personal access tokens unless an enterprise administrator enables them. Then register the server in C1 with the token.
https://api.githubcopilot.com/mcp/ under the connected user’s session, then returns the result. C1 doesn’t reshape or add to GitHub’s tools, and it enables all of GitHub’s toolsets.Before you begin
- AI access management must be enabled for your tenant. See Enable AI access management.
- GitHub doesn’t support dynamic client registration for this server, so for per-user OAuth you first register a GitHub OAuth app and give C1 its client ID and client secret. If you’d rather not, use a personal access token.
- If your GitHub organization or enterprise is on a Copilot Business or Copilot Enterprise plan, GitHub’s MCP servers in Copilot policy may need to be enabled for users to reach the hosted server. Organization policies can also limit which OAuth apps and scopes are allowed. See GitHub’s guide to setting up the GitHub MCP server.
In your MCP server catalog, this option is listed as GitHub, distinct from the GitHub API entry. If you don’t see either, contact the C1 support team to enable it for your tenant.
Set up per-user OAuth
Per-user OAuth is the recommended way to connect. Each user authorizes individually, and every tool call runs under their own GitHub identity and permissions. Create the GitHub OAuth app first.1
In GitHub, go to Settings > Developer settings > OAuth Apps and select New OAuth App (or Register a new application if this is your first one). See GitHub’s guide to creating an OAuth app.
2
Fill in the registration form:
- Application name — a recognizable name such as
C1. - Homepage URL — your C1 tenant URL, or
https://www.c1.ai. - Authorization callback URL — set this exactly to whichever matches your C1 tenant’s domain. GitHub OAuth apps allow only one callback URL.
- Default instance:
https://accounts.conductor.one/auth/callback - EU data residency instance:
https://accounts.c1eu.ai/auth/callback
- Default instance:
3
Select Register application, then copy the Client ID.
4
Select Generate a new client secret and copy the secret. GitHub shows it only once. Store it securely. If it’s ever exposed, generate a new one, update C1, then delete the old one (best practices for creating an OAuth app).
1
Follow Register an MCP server and select GitHub from the catalog.
2
When you configure authentication, choose OAuth2 — per-user passthrough and enter your OAuth app’s client ID and client secret.
3
Save your changes.
GitHub OAuth endpoints and scopes
Users authorize through GitHub’s standard OAuth web application flow with PKCE (S256). These are GitHub’s OAuth endpoints for your OAuth app, and you don’t enter them in C1:- Authorization URL:
https://github.com/login/oauth/authorize - Token URL:
https://github.com/login/oauth/access_token
repo— full access to public and private repositories, including code, commit statuses, invitations, collaborators, deployment statuses, and webhooks.read:org— read-only access to organization membership, organization projects, and team membership.read:user— read access to the user’s profile data.user:email— read access to the user’s email addresses.read:packages— download and install packages from GitHub Packages.write:packages— upload and publish packages to GitHub Packages.read:project— read-only access to user and organization projects.project— read and write access to user and organization projects.gist— write access to gists.notifications— read notifications, mark threads as read, and manage watch and thread subscriptions.offline_access— lets GitHub issue a refresh token so users stay connected without reauthorizing each time the access token expires.
workflow— add and update GitHub Actions workflow files. Needed when the file-writing tools change files under.github/workflows/.admin:org— fully manage the organization and its teams, projects, and memberships. Needed to create organization rulesets and write organization custom properties.read:enterprise— read enterprise profile data. Needed to read enterprise-level rulesets and custom properties.admin:enterprise— fully manage the enterprise. Needed to create enterprise rulesets and write enterprise custom properties.
Use a personal access token instead
GitHub’s hosted MCP server also accepts a personal access token, either fine-grained or classic, as a shared bearer credential. Every user then acts as one GitHub identity. Generate the token first.1
In GitHub, go to Settings > Developer settings > Personal access tokens. GitHub recommends Fine-grained tokens, which you can limit to specific repositories and permissions. A classic token reaches every repository its owner can access, and it’s the option that works across several organizations (managing personal access tokens).
2
Select Generate new token, set a name, an expiration, and the permissions or scopes you need, then select Generate token.
3
Copy the token. GitHub shows it only once.
1
Follow Register an MCP server and select GitHub from the catalog.
2
When you configure authentication, choose Bearer token and paste the token. C1 sends it as
Authorization: Bearer <token> on every request.How GitHub MCP credentials are shared
- Per-user OAuth. Each user authorizes with their own GitHub account, so tool calls run under that user’s GitHub identity and GitHub attributes each action to them.
- Personal access token. Every user’s tool calls use the one token you provided, so GitHub sees a single shared identity. C1 still attributes each call to the individual user in the AI tool usage audit log.
Tool coverage
The tools are the ones GitHub’s hosted server publishes, grouped by GitHub into toolsets such as repositories, issues, pull requests, Actions, code security, secret protection, Dependabot, security advisories, discussions, projects, gists, notifications, organizations, users, labels, Git data, Copilot, and stargazers. Because GitHub controls the list, tool names and coverage can change when GitHub updates its server. See GitHub’s toolset documentation for the current list.Discover and govern tools
After you register the server, C1 runs tool discovery against GitHub’s hosted MCP server. Discovered tools appear on the server’s Tools tab.Each tool starts as either Pending review or automatically Approved, depending on the option chosen when the server was set up or your tenant’s default tool settings in AI > MCPs > Settings. See Require tool approval and Default tool classification. C1 doesn’t set special approval levels for GitHub’s tools, so review the tools that merge, push, trigger workflows, or change repository settings before approving them.Before anyone can call a GitHub tool, it must be approved, added to a toolset, and bound to an access profile. Continue to Govern tools and toolsets to set this up.Tool discovery runs even if authentication isn’t complete yet, so seeing discovered tools doesn’t confirm a user has authorized. You confirm access when an approved user successfully calls a GitHub tool from their AI client.
Manage access to GitHub MCP
- Rotate the OAuth client secret on your OAuth app’s settings page in GitHub (Settings > Developer settings > OAuth Apps), then update the secret on the server’s authentication settings in C1.
- Rotate a personal access token by generating a new one in GitHub and updating it in C1. Set an expiration on the token so it rotates on a schedule.
- An individual user can revoke their own authorization at any time. In GitHub, go to Settings > Applications > Authorized OAuth Apps, then select Revoke next to C1 (reviewing your authorized OAuth apps).
- An organization owner can restrict or revoke OAuth app access org-wide if the organization has third-party application access restrictions enabled (about OAuth app access restrictions).
Troubleshooting GitHub access errors
If a tool call fails with a 403 error or returns empty results, check these causes:- SAML enforcement. If GitHub reports that the resource is protected by organization SAML enforcement, authorize the personal access token for single sign-on, or have the user sign in to the organization and authorize the OAuth app again.
- OAuth app access restrictions. If the organization restricts third-party OAuth apps, an organization owner must approve the app (about OAuth app access restrictions).