GitHub MCP
Connecting the GitHub MCP allows Apono Agent Privilege Guard to grant AI agents controlled, temporary access to GitHub resources. After completing the integration, you can create agentic access flows that govern how AI agents access your GitHub instance.
Prerequisites
Apono Connector
On-prem connection serving as a bridge between a GitHub instance and Apono:
Agent Privilege Guard
Agent Privilege Guard is enabled for your organization.
GitHub OAuth app
OAuth app registered to your GitHub organization
Learn how to create a GitHub OAuth app.
GitHub Client ID
Unique identifier of the GitHub OAuth app
Apono uses this ID in place of a secret during integration.
GitHub OAuth Scopes
GitHub permissions each user consents to, defining what the AI agent can access
Learn more about scopes for OAuth apps.
Integrate the GitHub MCP
Follow these steps to complete the integration:
On the Catalog tab, click GitHub (MCP OAuth). The Connect Integration page appears.
Under Discovery, click Next. The Apono connector section expands.
From the dropdown menu, select a connector. Choosing a connector links Apono to all the services available on the account where the connector is located.
If the desired connector is not listed, click + Add new connector and follow the instructions for creating a connector (AWS, Azure, GCP, Kubernetes).
Click Next. The Integration Config section expands.
Define the Integration Config settings.
SettingDescriptionIntegration Name
Unique, alphanumeric, user-friendly name used to identify this integration when constructing an access flow
GitHub Client ID
Unique identifier of the GitHub OAuth app
GitHub OAuth Scopes
GitHub permissions each user consents to, defining what the AI agent can access
Example (comma-separated list): repo,read:org,read:user
Click Next. The Get more with Apono section expands.
Define the Get more with Apono settings.
SettingDescriptionCustom Access Details
(Optional) Instructions explaining how to access this integration's resources Upon accessing an integration, a message with these instructions will be displayed to end users in the User Portal. The message may include up to 400 characters. To view the message as it appears to end users, click Preview.
Integration Owner
(Optional) Fallback approver if no resource owner is found Follow these steps to define one or several integration owners:
From the Attribute dropdown menu, select User or Group under the relevant identity provider (IdP) platform.
From the Value dropdown menu, select one or multiple users or groups.
NOTE: When Resource Owner is defined, an Integration Owner must be defined.
Resource Owner
(Optional) Group or role responsible for managing access approvals or rejections for the resource Follow these steps to define one or several resource owners:
Enter a Key name. This value is the name of the tag created in your cloud environment.
From the Attribute dropdown menu, select an attribute under the IdP platform to which the key name is associated. Apono will use the value associated with the key (tag) to identify the resource owner. When you update the membership of the group or role in your IdP platform, this change is also reflected in Apono.
NOTE: When this setting is defined, an Integration Owner must also be defined.
(Recommended) Click Test Integration to validate the integration.
Test Integration is available after you have entered or selected values for all required integration fields.
During the test, Apono runs the following validation checks:
Connectivity: The connector can reach the integration.
Configuration: The integration is set up correctly.
Authentication: The credentials are valid.
Discovery: Resources can be fetched.
The Test Validation checklist shows the result of each check.
If a check fails, Apono identifies the failed check and highlights the fields that need correction.
Click Confirm.
Now that you have completed the integration, you can create an agentic access flow that grants permission to your GitHub instance.
Last updated
Was this helpful?