Connect GitHub
Agents search repos, issues and code, read files and open pull requests; connect by signing in to GitHub or by pasting a fine-grained personal access token.
Repos, issues, pull requests, Actions and code search.
Once GitHub is connected, an agent can search repositories, issues and code, read files on a branch, open small pull requests and read the review comments back, and check Actions runs.
Before you start
- A GitHub account with access to the repositories the agents should see.
- If your organisation has Copilot Business or Enterprise, the policy MCP servers in Copilot must be enabled; the hosted GitHub server runs on the Copilot API.
- You must be an owner or admin of the woble workspace.
If the woble operator has registered a GitHub App once, you simply sign in. Otherwise the dialog asks for a fine-grained personal access token.
Connect it
- Open Marketplace, go to the Integrations tab, find GitHub and press Connect.
- If the dialog says you will sign in at GitHub: press Continue with GitHub. A new tab opens at github.com. Sign in, review the requested access (repositories, organisation membership, notifications, projects), choose which organisations to grant and press Authorize. The tab closes.
- If the dialog shows a field named Fine-grained personal access token: on GitHub open your profile picture, Settings, Developer settings, Personal access tokens, Fine-grained tokens, Generate new token. Set a name and expiry, choose the Resource owner (you or your organisation), pick Repository access, and under Permissions tick at least Contents, Issues and Pull requests (read and write), plus Actions read for workflow runs. Press Generate token, copy it (shown once), paste it into the field and press Connect.
- The card shows Connected and the agent panel lists the new GitHub tools.
Or ask an agent
Type @ruby connect GitHub in any chat. The same card appears in the conversation. Only owners and admins can complete it.
Try it
- "@atlas list the open pull requests in acme/api and summarise the one waiting longest for review."
If it does not connect
- Organisation repositories missing: the token's resource owner is your personal account, the organisation marked the token pending until an admin approves it, or SAML SSO requires authorising the token or app for that organisation.
- Token expired or revoked: press Test connection in Marketplace, Connected; if it fails, Remove and connect again with a new token.
- No sign-in option: the operator has not registered the GitHub App yet, so only the token route is available.
Disconnect
Open Marketplace, Connected, and press Remove on GitHub. The stored token is deleted and agents lose the GitHub tools immediately.
More in this category
LinearIssues, projects and cycles for product teams.
Jira and ConfluenceAtlassian issues, boards and pages.
SentrySearch, triage and analyse issues, traces and releases.
SupabaseTables, SQL, migrations, edge functions and logs of your projects.
Neon PostgresProjects, branches and SQL on serverless Postgres.
AppwriteAuth users, databases, storage, functions, sites and messaging.