Skip to main content
The GitHub integration exposes selected repository reads through a local MCP server. Use Connect to select the profile and configure access for the repositories your agent needs.

​
Operations

​
Account setup

Supply a GitHub token with access to the intended repositories through the host’s credential controls. The server receives it as GITHUB_PERSONAL_ACCESS_TOKEN. Use a separate process for each account and retire that process when changing accounts.

​
Direct MCP configuration

The selected server runs over stdio with:
The host selects the executable and child environment. Keep unrelated GitHub, proxy and logging settings out of that environment. Retain the bundled notices alongside the executable. After connection, inspect the tool list and apply the intended agent grants. For reproducible file reads, use a commit SHA. For commit lists, provide positive integer page and perPage values and consume returned pages explicitly.

​
Process and output handling

Set a caller deadline and retain process ownership through cleanup. Apply the host’s network and output controls to repository content and provider errors. File reads may involve additional tree or reference requests; resource links are resolved by the consuming host. See native MCP integration for attachment and access control for operation and resource permissions.