Skip to main content

GitHub

Where to issue a GitHub personal access token and connect it to Nora.
GitHub integrations let your agents read repos, open pull requests, comment on issues, and trigger workflow runs. Nora authenticates with a personal access token (PAT) sent as Authorization: Bearer <token>.

Where to apply for credentials

GitHub — Personal Access Tokens

Settings → Developer settings → Personal access tokens
GitHub offers two PAT shapes:
  • Fine-grained (Settings → Developer settings → Personal access tokens → Fine-grained tokens) — preferred. Pick specific repos and exact permissions.
  • Classic (Tokens (classic)) — broader, repository-level scopes. Easier for dev.

Required scopes

Pick the smallest scope that covers your agent’s behavior:
Scope (classic)When to use
repoFull read/write on private + public repos. Most agents need this.
read:userConnectivity test — Nora calls GET /user to verify
workflowIf your agent triggers GitHub Actions runs
read:orgIf your agent enumerates org members or teams
For fine-grained tokens, equivalent permissions live under Repository permissions (Contents, Pull requests, Issues, Workflows).

Connect in Nora

1

Open the GitHub integration

From an agent’s detail page, open the Integrations tab and find GitHub.
2

Paste the token

Paste your PAT into the Personal Access Token field. Optionally set an organization name.
3

Connect

Click Connect. Nora calls GET https://api.github.com/user with the token and reports your GitHub login on success.

MCP server

GitHub maintains an official MCP server:
  • Package: @github/github-mcp-server
  • Docs: github.com/github/github-mcp-server
  • Env: GITHUB_PERSONAL_ACCESS_TOKEN — Nora injects GITHUB_TOKEN, set the MCP env var to that value at startup.

Environment variables Nora injects

VariableSource
GITHUB_TOKENPersonal Access Token
GITHUB_ORGOrganization (if set)