Skip to main content
The github MCP adapter wraps the GitHub REST API. Use it to triage issues, review pull requests, sync repo metadata, and post updates when workflows complete — without leaving AgentRuntime.

Prerequisites

  • A GitHub account with access to the repositories you will automate
  • A personal access token (classic or fine-grained) with scopes for those repos (repo, read:org as needed)
  • project_contributor access in your AgentRuntime workspace

Connect in AgentRuntime

1

Create a GitHub connection

Go to Connections and click New custom connection to create an API key connection. Paste your GitHub token as the secret. Store the token in a connection profile — never in workflow JSON.
2

Add github MCP instance

Go to MCP, click Add instance for github, wire your connection on Instance config, set the profile active, and save.
3

Verify access

Run a test workflow with mcp_callget_authenticated_user to confirm the token works before automating production repos.
See Authentication for how connections bind to MCP instances.

What you can build

  • PR release assistant — On webhook or schedule: list_pull_requestsget_pull_request + list_pull_request_files → LLM summary → add_issue_comment or Gmail notify reviewers.
  • Issue triagelist_issues with labels filter → LLM classify → update_issue to add labels and assignees.
  • Changelog draftcompare_commits between tags → LLM generate notes → create_or_update_file on CHANGELOG.md → optional human_task before merge.
  • Onboarding repo scansearch_repositories or list_reposget_file_contents for README → store metadata in Postgres for internal dashboards.

Tools

Pull requests & branches

Issues & comments

Repository & code

Search & users

Example

Comment on a PR after an automated check passes:

Configuration

Troubleshooting