GitHub Integration
GitHub is connected via both MCP server (for Claude Code sessions) and CLI (gh command, for automated routines). The @atlas agent uses it for PR reviews, issue tracking, release management, and code search.
MCP Setup
The GitHub MCP server is configured in.claude/settings.json. If you selected GitHub during make setup, it is already configured.
To verify or add it manually, ensure this entry exists in .claude/settings.json:
Creating a Personal Access Token
- Go to github.com/settings/tokens
- Click Generate new token (classic) or use Fine-grained tokens
- Select scopes:
repo— full repository access (PRs, issues, code)read:org— read org membership (for team queries)read:user— read user profile
- Copy the token and add it to the MCP config above
What It Can Do
The GitHub MCP server exposes tools for:Using GitHub in Claude Code
Once the MCP is configured, you can interact with GitHub naturally:Automated Routines
The @atlas agent runs GitHub reviews on schedule using theint-github-review skill:
The GitHub review checks:
- Open PRs needing review
- Community issues (bug reports, feature requests)
- Recent releases
- Stars and fork trends
- Contributor activity
Testing
gh CLI
Some routines also use thegh CLI (GitHub’s official command-line tool). It authenticates separately:
gh CLI is used by the runner scripts for operations that are simpler via CLI than MCP (e.g., checking PR merge status, listing workflow runs).
Configuring Repositories
Set the repositories to monitor inconfig/workspace.yaml:
Troubleshooting
“Bad credentials” — Your personal access token is expired or revoked. Generate a new one and update.claude/settings.json.
MCP server not starting — Run npx -y @modelcontextprotocol/server-github manually to check for errors. Ensure Node.js 18+ is installed.
Rate limiting — GitHub allows 5,000 requests/hour for authenticated users. If you hit limits, the MCP returns a rate-limit error. Wait or use a token with higher limits (GitHub App installation token).