Skip to main content

​
Overview

Integrate GitHub to manage repositories, issues, pull requests, and automate development workflows directly from CORE. Access 60+ tools for complete GitHub operations without leaving your workspace.

​
Setup Guide

  • Authentication Type : OAuth 2.0

​
How to Connect

  1. Navigate to CORE Dashboard → Integrations
  2. Click on the GitHub card
  3. Click Connect to authorize CORE
  4. You’ll be redirected to GitHub to authorize the application
  5. Grant the required permissions
  6. You’ll be redirected back to CORE once connected

​
Use Cases

​
Action Use Cases

When you ask CORE to perform GitHub tasks, it uses MCP tools to execute your requests:
Scenario: Automatically create and track GitHub issues from other tools
"Create a GitHub issue in the 'core' repo titled 'Add user authentication'
with the description 'Need to implement OAuth2 authentication'
and assign it to @username with labels 'feature' and 'high-priority'"
The agent will use create_issue to create the issue and can follow up with create_issue_comment to add additional context or use update_issue to modify details.
Scenario: Review and merge pull requests directly from your IDE
"Show me all open pull requests in the main repository,
then review PR #123 and merge it if tests are passing"
The agent will:
  1. Use list_pull_requests to fetch open PRs
  2. Use get_pull_request to get PR details
  3. Check list_workflow_runs for CI status
  4. Use merge_pull_request to merge after verification
Scenario: Find specific code patterns across your repositories
"Search for all files using the deprecated API endpoint
'/api/v1/auth' across all my repositories"
The agent will use search_code to find matching files and can use get_file_content to read the actual implementations for analysis.
Scenario: Automate release workflows
"Create a new release branch 'release-v2.0' from main,
update the version in package.json to 2.0.0,
and create a pull request for the release"
The agent will:
  1. Use create_branch to create the release branch
  2. Use create_or_update_file to update version files
  3. Use create_pull_request to create the release PR
  4. Use create_issue to track release tasks
Scenario: Track team activity and respond to notifications
"Show me all issues assigned to me that were updated in the last 24 hours,
and mark all my notifications as read"
The agent will use list_issues with appropriate filters, list_notifications to keep you updated, and mark_all_notifications_read to clear your notifications.
Scenario: Monitor and control GitHub Actions workflows
"Check the status of the latest workflow run on the main branch.
If it failed, rerun it"
The agent will:
  1. Use list_workflow_runs to get recent runs
  2. Use get_workflow_run to check status details
  3. Use rerun_workflow if the run failed
Scenario: Quickly set up new repositories with standard configurations
"Create a new repository called 'my-new-project',
add a README, create labels for 'bug', 'feature', and 'documentation',
and set up a milestone for 'v1.0'"
The agent will:
  1. Use create_repository to create the repo
  2. Use create_or_update_file to add the README
  3. Use create_label for each label
  4. Use create_milestone for the v1.0 milestone
Scenario: Automated code review and feedback
"Review the latest PR in my repository, check for any TODO comments
in the changed files, and create review comments for each one"
The agent will:
  1. Use list_pull_requests to get the latest PR
  2. Use get_pull_request to get changed files
  3. Use get_file_content to read files
  4. Use create_pr_comment to add review comments

​
Proactive Use Cases

With webhooks enabled, CORE monitors GitHub 24/7 and acts automatically based on your instructions:
Trigger: New issue created with specific labelsAutomated Action: Assign to team member and add to project
"When a new issue is created with the 'bug' label,
automatically assign it to @devops-team,
add it to the 'Current Sprint' project,
and notify me on WhatsApp"
CORE monitors new issues and automatically routes them based on labels, keeping your team organized without manual triaging.
Trigger: Pull request review requestedAutomated Action: Notify on preferred channel with context
"When I'm requested to review a PR,
send me a Slack DM with the PR title, description, and changed files summary"
Never miss review requests. CORE watches for review assignments and notifies you with full context on your preferred channel.
Trigger: Workflow run fails on main branchAutomated Action: Create issue and escalate
"When a workflow fails on the main branch,
create a high-priority issue with the error logs,
assign it to the last committer,
and send an urgent notification to #engineering on Slack"
Instantly respond to build failures. CORE creates issues, assigns responsibility, and escalates critical failures automatically.
Trigger: New release publishedAutomated Action: Extract changelog and notify stakeholders
"When a new release is published,
extract the changelog from the release notes,
save it to CORE memory with label 'releases',
and send a summary to #product-updates on Slack"
Keep everyone informed on releases. CORE tracks release activity, stores release notes, and broadcasts updates across channels.
Trigger: PR updated after 30 days of inactivityAutomated Action: Add comment and close if inactive
"When a PR hasn't been updated in 30 days,
add a comment asking if it's still relevant,
and if no response in 7 days, close it with a standard message"
Maintain repository hygiene automatically. CORE monitors stale PRs and handles cleanup based on your rules.
Trigger: Dependabot security alert createdAutomated Action: Create issue and notify security team
"When a security vulnerability is detected,
create a critical-priority issue in the 'security-fixes' project,
notify the security team on Slack,
and add it to CORE memory for tracking"
Respond to security issues instantly. CORE escalates vulnerabilities, creates tracking issues, and notifies the right team members.

​
Scopes

  • repo - Repository access (read/write)
  • repo:status - Commit status access
  • repo_deployment - Deployment status access
  • public_repo - Public repository access
  • repo:invite - Repository invitations
  • security_events - Security events access
  • write:repo_hook - Repository webhooks
  • read:repo_hook - Read repository webhooks
  • admin:org - Organization administration
  • write:org - Organization membership
  • read:org - Read organization data
  • admin:public_key - Public key administration
  • write:public_key - Public key write access
  • read:public_key - Public key read access
  • admin:org_hook - Organization webhooks
  • gist - Gist access
  • notifications - Notifications access
  • user - User profile access
  • read:user - Read user profile
  • user:email - User email access
  • user:follow - Follow/unfollow users
  • delete_repo - Delete repositories
  • write:discussion - Discussions write access
  • read:discussion - Discussions read access
  • write:packages - Packages write access
  • read:packages - Packages read access
  • delete:packages - Delete packages
  • admin:gpg_key - GPG key administration
  • write:gpg_key - GPG key write access
  • read:gpg_key - GPG key read access
  • workflow - Workflow access

​
Available MCP Tools

The GitHub integration provides 60+ tools for comprehensive repository management:
Tool NameDescription
get_repoGet details of a specific repository
list_reposList repositories for the authenticated user
create_repositoryCreate a new repository
fork_repositoryFork an existing repository
search_repositoriesSearch repositories across GitHub

​
Triggers

GitHub triggers enable CORE’s Meta Agent to wake up and act proactively when events are detected via scheduled polling.
EventDescription
GITHUB_ISSUE_CREATEDTriggered when a new issue is opened in the repository
GITHUB_ISSUE_UPDATEDTriggered when an issue is edited or modified
GITHUB_ISSUE_CLOSEDTriggered when an issue is closed
GITHUB_ISSUE_REOPENEDTriggered when a closed issue is reopened
GITHUB_ISSUE_ASSIGNEDTriggered when an issue is assigned to a user
GITHUB_ISSUE_LABELEDTriggered when a label is added to an issue

​
Need Help?

Join our Discord community for support in #core-support