Gap discovered during claude-agent-platform setup
GITHUB_SCOPES in /opt/github-mcp-auth/.env currently requests:
repo, read:org, read:user, read:project
This blocks the github MCP from creating or updating files under .github/workflows/* in any repo (GitHub returns 404 for write attempts without the workflow scope, even when repo is granted).
Repro
github:create_or_update_file(path=".github/workflows/foo.yml")
# → 404 Not Found
Fix
- Add
workflow to GITHUB_SCOPES in .env
- Restart
github-mcp-auth.service
- Existing OAuth tokens in DB won't auto-upgrade — users need to disconnect + reconnect the github MCP in their Claude.ai settings to mint a new token with the additional scope.
Why it matters
Without this, any agent flow that involves provisioning GitHub Actions workflows (claude-agent-platform setup, CI bootstrapping, reusable-workflow rollouts) has to fall back to a separate PAT or VPS-side gh CLI auth, which fragments credential management.
References
Gap discovered during claude-agent-platform setup
GITHUB_SCOPESin/opt/github-mcp-auth/.envcurrently requests:This blocks the github MCP from creating or updating files under
.github/workflows/*in any repo (GitHub returns 404 for write attempts without theworkflowscope, even whenrepois granted).Repro
Fix
workflowtoGITHUB_SCOPESin.envgithub-mcp-auth.serviceWhy it matters
Without this, any agent flow that involves provisioning GitHub Actions workflows (claude-agent-platform setup, CI bootstrapping, reusable-workflow rollouts) has to fall back to a separate PAT or VPS-side
ghCLI auth, which fragments credential management.References
workflowscope grants ability to add/update.github/workflows/*files