github_app_access
Diagnose GitHub App installation access and return browser setup links without scraping GitHub.
Connect and discover
Section titled “Connect and discover”Connect an authenticated MCP client. Call tools/list to confirm this tool is available to the current credential. Provider, workspace, and agent grants remain separate access checks.
Input fields
Section titled “Input fields”| Field | Type | Required | Description |
|---|---|---|---|
action |
"diagnose" · "start_install" · "list_installations" |
Yes | Operation to perform. Choose one advertised value; the remaining parameters are interpreted for that action. |
owner |
string | No | Repository owner or organization login. |
repo |
string | No | Repository name without the owner prefix. |
target |
string | No | Explicit source or repository destination used by the selected action. |
redirectTo |
string | No | Safe Commentary-relative destination to return to after GitHub App setup. |
Call the tool
Section titled “Call the tool”Send a tools/call request with name: "github_app_access" and an arguments object containing the required fields above. Choose an advertised action, then supply the fields required by that action. Do not treat a successful request as human approval or verified execution unless the returned contract explicitly records that fact.
Errors and recovery
Section titled “Errors and recovery”Read the returned error and permission requirements. Refresh stale revisions before conditional writes, retain idempotency keys only for exact retries, and reconnect when a credential has expired.
Complete input contract
Section titled “Complete input contract”Download the JSON schema for action-specific unions, nested fields, and validation constraints. This schema is generated from the same released definitions as the MCP endpoint. Browse tools.