GitHub MCP integration for AI agents.
Connect AI agents to GitHub repositories, commits, issues, branches, pull requests, releases, and workflow context through structured actions.
- ACTION CONTRACTS
- 145
- AUTHENTICATION
- OAuth 2.0 + API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the GitHub integration exposes
The Working Machines GitHub Agent App gives an authorized agent named operations over repositories and their development lifecycle. Instead of navigating repository pages, the agent can inspect a contract for an action, provide the required owner and repository identifiers, and receive a structured result.
A useful GitHub workflow normally begins with read actions: identify the current account, inspect a repository, list commits, or retrieve an issue. Writes such as creating an issue, opening a pull request, changing a reference, or deleting a repository should use narrower credentials and an explicit confirmation boundary.
VERIFIED ACTION SAMPLE
Real GitHub capabilities.
Showing 12 of 145 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
check_pull_request_mergedREADCheck whether a GitHub pull request has been merged.
INPUTS: owner / repo / pullNumber
add_issue_assigneesWRITEAdd assignees to a GitHub issue.
INPUTS: owner / repo / issueNumber / assignees
cancel_workflow_runHIGH IMPACTCancel a GitHub Actions workflow run.
INPUTS: owner / repo / runId
clear_issue_labelsREVIEWRemove all labels from a GitHub issue.
INPUTS: owner / repo / issueNumber
add_issue_labelsWRITEAdd labels to a GitHub issue.
INPUTS: owner / repo / issueNumber / labels
add_repository_collaboratorWRITEAdd a collaborator to a GitHub repository or update their permission.
INPUTS: owner / repo / username / permission
check_repository_starredREADCheck whether the authenticated user has starred a GitHub repository.
INPUTS: owner / repo
compare_commitsREVIEWCompare two commit references in a GitHub repository.
INPUTS: owner / repo / basehead / perPage / page
create_commit_commentWRITECreate a comment on a commit in a GitHub repository.
INPUTS: owner / repo / commitSha / body / path
create_commit_statusREADCreate a commit status for a GitHub commit SHA.
INPUTS: owner / repo / sha / state / context
create_issueWRITECreate an issue in a GitHub repository.
INPUTS: owner / repo / title / body / assignees
create_issue_commentWRITECreate a comment on a GitHub issue.
INPUTS: owner / repo / issueNumber / body
INPUT CONTRACTS
Know what the action needs before it runs.
check_pull_request_merged
ownerREQUIREDrepoREQUIREDpullNumberREQUIRED
add_issue_assignees
ownerREQUIREDrepoREQUIREDissueNumberREQUIREDassigneesREQUIRED
cancel_workflow_run
ownerREQUIREDrepoREQUIREDrunIdREQUIRED
clear_issue_labels
ownerREQUIREDrepoREQUIREDissueNumberREQUIRED
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Incident follow-up
Correlate a Sentry finding with recent commits, then create a GitHub issue containing the sanitized technical context.
Release coordination
Inspect commits and branches, verify the intended head and base, and open a pull request only after user review.
Repository maintenance
List stale issues or branches and prepare a proposed cleanup plan before any deletion or closure.
SAFETY BOUNDARY
Operate GitHub with explicit limits
- Use a GitHub App or token limited to the required repositories.
- Confirm repository owner, repository, branch, head, and base before a write.
- Treat deletion, merge, permission, and release operations as high-impact actions.
- Verify the returned issue or pull-request URL before reporting completion.
CONNECTION MODEL
OAuth 2.0 + API key
GitHub personal access token used with the Authorization Bearer header. Fine-grained tokens are recommended.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 80
- WRITE SIGNALS
- 31
- HIGH IMPACT
- 16
- REVIEW SIGNALS
- 18
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by GitHub.