GitHub for AI agents

Host code, review pull requests, track issues, and automate development workflows. Sign in once through OAuth and every agent you run can use it.

  • Signs in with OAuth
  • Ready to connect
  • Any MCP client
  • No card required

The route from an agent to GitHub

Once GitHub is set up in your workspace, any agent you run can reach it: a Spinrun agent, or Claude, ChatGPT and Cursor through one MCP endpoint. Every call passes through the Spinrun gateway, which sorts it by risk and writes it to the activity log.

By default, every change an agent makes in a connected app waits for your approval, on every plan. Enhanced Control adds per-app read, write and destructive rules at the gateway on Free and Pro.

GitHub in the catalog

Host code, review pull requests, track issues, and automate development workflows. · Developer Tools & DevOps

  1. An agent gets a jobFrom chat, a schedule, or your own AI client
  2. Spinrun checks the callSorted as a read, a write or a destructive call
  3. GitHub does the workThrough the connection you set up in your workspace
  4. Every call is loggedTool, outcome and duration, in one activity log

From Spinrun recipes

Jobs to hand an agent in GitHub

Each one is a real prompt from a Spinrun recipe or team page, ready to adapt to your own work.

  • “Turn this Slack thread into a Linear ticket: extract repro steps, search our GitHub for related code and duplicate issues, file it with priority and links, then post the ticket back to the thread.”

    From bug report to filed ticket

  • “Is PR #1247 safe to merge? Leave line comments where it could be cleaner and one comment that sums up your verdict.”

    Merge or not

  • “What carries into next sprint, and what did this one deliver? Answer on a Notion page using Linear and GitHub.”

    Sprint closeout page

  • “Warn #eng-payments about the jump in Sentry errors on /api/charge, with the fix you'd make and the deploy that caused it.”

    Error spike

Three steps

From connection to first call

  1. Connect an app once

    Sign in from your workspace with OAuth or an API key. Spinrun keeps the credential in an encrypted vault, never in an agent's config.

  2. Decide what it may do

    By default, every change an agent makes in a connected app waits for your approval, on every plan. Enhanced Control adds per-app rules for reads, writes and destructive calls on Free and Pro.

  3. Let any agent use it

    Claude, ChatGPT, Cursor or a Spinrun agent reach the app through one MCP endpoint, and every call is written to the same activity log.

What it can do

Every GitHub action, sorted by risk

Spinrun sorts every GitHub action into one of three tiers. By default, agents ask before a write; on Free and Pro, the rules you set decide which tiers run.

  • Writes

    Accept a repository invitation

    GITHUB_ACCEPT_A_REPOSITORY_INVITATION

    Accepts a pending repository invitation that has been issued to the authenticated user.

  • Writes

    Add a repository collaborator

    GITHUB_ADD_A_REPOSITORY_COLLABORATOR

    Adds a github user as a repository collaborator, or updates their permission if already a collaborator; `permission` applies to organization-owned repositories (personal ones default to 'push' and ignore this field), and an invitation may be created or permissions updated directly.

  • Writes

    Add a repository to an app installation

    GITHUB_ADD_A_REPOSITORY_TO_AN_APP_INSTALLATION

    Adds a repository to a github app installation, granting the app access; requires authenticated user to have admin rights for the repository and access to the installation.

  • Writes

    Add a selected repository to a user secret

    GITHUB_ADD_A_SELECTED_REPOSITORY_TO_A_USER_SECRET

    Grants a specified repository access to an authenticated user's existing codespaces secret, enabling codespaces created for that repository to use the secret.

  • Writes

    Add app access restrictions

    GITHUB_ADD_APP_ACCESS_RESTRICTIONS

    Replaces github app access restrictions for an existing protected branch; requires a json array of app slugs in the request body, where apps must be installed and have 'contents' write permissions.

  • Writes

    Add assignees to an issue

    GITHUB_ADD_ASSIGNEES_TO_AN_ISSUE

    Adds or removes assignees for a github issue; changes are silently ignored if the authenticated user lacks push access to the repository.

  • Writes

    Add email for auth user

    GITHUB_ADD_AN_EMAIL_ADDRESS_FOR_THE_AUTHENTICATED_USER

    Adds one or more email addresses (which will be initially unverified) to the authenticated user's github account; use this to associate new emails, noting an email verified for another account will error, while an existing email for the current user is accepted.

  • Writes

    Add labels to an issue

    GITHUB_ADD_LABELS_TO_AN_ISSUE

    Adds labels (provided in the request body) to a repository issue; labels that do not already exist are created.

  • Writes

    Add or update team membership for a user

    GITHUB_ADD_OR_UPDATE_TEAM_MEMBERSHIP_FOR_A_USER

    Adds a github user to a team or updates their role (member or maintainer), inviting them to the organization if not already a member; idempotent, returning current details if no change is made.

Paired in recipes

Apps agents use with GitHub

These appear next to GitHub in Spinrun's templates, recipes and team pages.

Same category

Other Developer Tools & DevOps apps

Other apps in this category that your agents can use.

See every app in this category

Questions about GitHub

You approve GitHub in its own sign-in window. Spinrun keeps the token in an encrypted vault, refreshes it before it expires, and you can revoke it in one click.

Put GitHub to work. Start free.

Connect GitHub, decide what it may do, and give an agent its first job.

Before anything loads

We would like to switch on analytics, so we can see which pages are worth keeping. Nothing has loaded yet and nothing will until you choose. The cookies that keep you signed in and remember your language are not part of this.

Read the Cookie Policy