Skip to main content
Status: Available. GitHub uses GitHub’s hosted MCP server. You sign in with GitHub through the ApexGenius Connect app and choose the repositories it can read. Nothing is pasted. Every connection starts read-only: ApexGenius sends GitHub’s read-only header, so your AI can read repositories, files, code search, commits, releases, issues and pull requests, and cannot change anything. On the connection page you can switch one connection to read and write for a list of repositories, including creating, reviewing and merging pull requests. Deleting files, and creating, deleting or forking repositories stay blocked everywhere. Explore the GitHub connector. Add ApexGenius to your AI agent first: Add your AI agent. Then connect GitHub here.

Sign in with GitHub

Choose Connect on the GitHub connection page and sign in to GitHub to approve the ApexGenius Connect app. Then choose Choose repos on GitHub and install the app on the repositories your AI may read; GitHub brings you back to ApexGenius. The app reaches only the repositories it is installed on, and its sign-in renews itself. For a repository owned by an organization, an owner may need to approve the app. An organization can require approval for the app. If a repository is missing, check the app installation, then the organization’s policy.

Connect and read your first repository

Before you start
  • A GitHub account that can read the repositories you want your AI to use.
  • For a repository owned by an organization, an owner who can approve the ApexGenius Connect app.
1

Open GitHub in Connections

Sign in to ApexGenius, open Connections, choose GitHub, and select Connect.
The ApexGenius Connections page with GitHub in the Available group and its Connect button.

Open Connections and find GitHub. Until you connect it, its row shows Connect.

2

Sign in to GitHub

GitHub asks which account to use. Choose Continue on the one you want and approve the ApexGenius Connect app. Nothing is pasted, and the sign-in renews itself.
GitHub's Select user to authorize ApexGenius Connect page, with the account names blurred and a red box around the Continue row.

GitHub asks which account to use. Choose Continue on the one you want. Account names are blurred in this capture.

3

Choose your repositories

Pick your account or an organization, choose Only select repositories, pick the ones your AI may use, and select Install. GitHub brings you back to ApexGenius. Add more later with Choose repos on GitHub on the connection page. An organization owner may need to approve the app.
The GitHub page in ApexGenius with the status control menu open, showing Check again and Choose repos on GitHub.

Back in ApexGenius, open the status control and choose Choose repos on GitHub to install the app on your repositories.

GitHub's Install ApexGenius Connect page asking where to install, listing a personal account (blurred) and an organization, with a red box around both.

Pick your account or an organization to install the ApexGenius Connect app on.

GitHub's Install ApexGenius Connect form with All repositories and Only select repositories, the permissions, and red boxes around Only select repositories and Install.

Choose Only select repositories, pick the ones your AI may use, then Install. ApexGenius keeps the connection read-only until you turn on writes.

4

Check the connected account

Your repositories appear on the connection Overview. Ask your AI the question below and compare the login with your GitHub account.
The GitHub connection Overview in ApexGenius showing a green Connected status, rows for Tools, Agents and Skill, recent calls, and one repository switched on with its name blurred.

After you connect, Overview shows Connected and lists your repositories. The repository name is blurred in this capture.

Try a first question with your AI agent
Confirm the login matches your GitHub account and the README matches the repository on github.com. If the README is missing, install the app on that repository with Choose repos on GitHub. New connections are read-only, so this check changes nothing. To let your AI open issues or open, review and merge pull requests, open the Tools tab on the connection, choose Settings, and switch to Read and write.

Turn on writes for selected repositories

Writes are off until you turn them on, one connection at a time. Each person does this on their own connection. Turning writes on for yourself does not turn them on for a teammate.
1

Switch on the repositories

Open Connections and choose GitHub. On Overview, check the Repositories list and switch on the repositories your AI may change. At least one is required for writes.
The GitHub Overview in ApexGenius with a red box around one repository row and its switch, turned on.

The Repositories list on Overview. Each repository has its own switch. The repository name is blurred.

2

Open Settings on the Tools tab

Open the Tools tab and choose Settings. A panel opens with GitHub access as its first block.
The Tools tab of the GitHub connection in ApexGenius with a red box around the Settings button.

Settings is on the Tools tab, to the right of Tool permissions.

3

Choose Read and write

Choose Read and write and select Turn on writes. The badge changes from Read only to Writes on.
The GitHub access panel in ApexGenius with a red box around Mode, showing Read only and Read and write, with Read and write selected.

Mode, under GitHub access. This capture shows a connection after writes are on, so the badge reads Writes on and the button reads Save access.

4

Tick Run workflows, if you need it

To let your AI run, rerun or cancel workflow runs, tick the repository under Run workflows and select Save access. A run uses the repository’s secrets, can deploy, and cannot be undone. Skip this if your AI only needs branches and pull requests.
The GitHub access panel in ApexGenius with a red box around Run workflows, one repository ticked, and the Save access button.

Run workflows appears once Read and write is on. Tick a repository, then select Save access. The repository name is blurred.

5

Check that writes are on

Ask your AI to discover GitHub tools again. It should now list write tools such as create_branch and push_files. That is your check that writes are on.
Connected does not mean writes are on. The GitHub page shows Connected for every working sign-in. To see whether your AI can change anything, check GitHub access for Read only or Writes on.
With a repository list set, reads stay inside it too: a call that names another repository is refused, searches get repo: filters for your repositories, and repository search is turned off. Switch back to Read only at any time; the change takes effect on the next call. Every write is recorded in the connection’s activity.

Every setting, and where it lives

GitHub has more settings than most apps. Each one belongs to a single connection, so every person sets their own. The status menu is the Connected control under the page title.
The GitHub connection in ApexGenius with the Tools tab selected and the settings panel open. A red box marks Mode, with Read only and Read and write.

Most settings live here: the Tools tab, then Settings. This capture shows a connection with writes on. The repository name is blurred.

Tools and the GitHub skill

Open Skills on the connection to read GitHub, or read that MCP prompt in a compatible AI client. It explains the first safe read, how to connect, the two modes and the tools below. Three ApexGenius tools route GitHub’s live catalog: GitHub documents these reads in its default toolsets: These writes run only on a read-and-write connection, and only in its repositories: Running workflows is off until you pick a repository for it on the connection page. A run uses the repository’s secrets, can deploy, and cannot be undone. PR merges use the same write access and repository list as other PR changes. Read the PR first, then pass its current head as expectedHeadSha so GitHub refuses the merge if new code was pushed in the meantime. A merge can trigger workflows and deployments even when manual workflow runs are off in ApexGenius. Read back the merged state and commit before reporting completion. Reverting the code does not undo deployments or other effects the merge triggered. Your AI discovers the tools with apex_search_tools, runs reads with apex_call_read_tool and writes with apex_call_write_tool. Approval works the same way on every ApexGenius connector: Writes run immediately. Blocked hides a tool from agents.

What is not exposed

delete_file, create_repository, delete_repository and fork_repository are refused on every connection, whatever GitHub allows, and are hidden from discovery. Do those on github.com, along with deleting workflow run logs. Dependabot, code scanning, discussions, gists, notifications and projects are not reached by this connection.

Troubleshooting

  • A repository is missing. A signed-in connection reaches only the repositories the app is installed on: choose Choose repos on GitHub and add it, or ask an organization owner to approve the app.
  • Your AI says GitHub is read-only, or it cannot push. The connection is still read-only. GitHub lists no write tools on a read-only connection, so your AI finds nothing to call. Turn on writes above, then ask your AI to discover GitHub tools again.
  • It works for you and not for a teammate. Writes are set on each person’s connection. Ask them to turn on writes on theirs.
  • A write was refused. The connection is read-only, the repository is not on its list, or the tool is one of the blocked four. The refusal names which. For a write GitHub itself rejects, check that the app is installed on that repository.

Official GitHub documentation

Last modified on November 13, 2026