What You'll Build
A GitHub workflow assistant that uses Continue with the GitHub MCP to:
- List, filter, and summarize open issues
- Review and summarize recently merged PRs
- Post comments with AI-generated summaries or checklists
- Automate routine GitHub maintenance with headless CLI runs
Prerequisites
Before starting, ensure you have:- Continue account with Hub access
- Read: Understanding Agents — How to get started with Hub agents
- Node.js 22+ installed locally
- A GitHub account and a repository to work with
- A GitHub token with the appropriate scopes:
- For read-only:
repo:read
- To comment on issues/PRs:
public_repo
for public repos orrepo
for private repos
- For read-only:
1
Install Continue CLI
2
Configure GitHub Token
Add your
GITHUB_TOKEN
to your Continue Hub agent’s environment variables.To use agents in headless mode, you need a Continue API key.
For write actions (e.g., posting comments), your token must include the relevant GitHub scopes.
GitHub MCP Workflow Options
🚀 Fastest Path to Success
Use the GitHub MCP from Continue Hub for one-click setup, or add it via CLI.
- ⚡ Quick Start (Recommended)
- 🛠️ Manual Setup
1
Install GitHub MCP via Continue Hub
Visit the Anthropic GitHub MCP on Continue Hub and click Install to add it to your agent.The listing provides a pre-configured MCP block; add your
GITHUB_TOKEN
in Hub.2
Launch the Agent
From your repo root:Now try: “List my open issues labeled bug and summarize priorities.”
You can also attach an MCP to a one-off session:
cn --mcp anthropic/github-mcp
.Agent Requirements
Agent Requirements
To use GitHub MCP with Continue CLI, you need either:
- Continue CLI Pro Plan with the models add-on, OR
- Your own API keys added to Continue Hub secrets
Issue Workflows
Use natural language to explore, triage, and act on open issues. The agent calls GitHub MCP tools under the hood.Where to run these workflows:
- IDE Extensions: Use Continue in VS Code, JetBrains, or other supported IDEs
- Terminal (TUI mode): Run
cn
to enter interactive mode, then type your prompts - CLI (headless mode): Use
cn -p "your prompt" --auto
for automation
Triage and Summaries
Summarize Open Issues
Get a prioritized overview of current open issues.TUI Mode Prompt:Headless Mode Prompt:
Owner/Label Filters
Narrow by label or assignee.TUI Mode Prompt:Headless Mode Prompt:
Taking Action
Comment on an Issue
Post an AI-generated status update or checklist.TUI Mode Prompt:Headless Mode Prompt:
Requires a token with permission to comment (
public_repo
or repo
). The agent will confirm before posting unless --auto
is used.Find Stale Issues
Identify issues that need attention.TUI Mode Prompt:Headless Mode Prompt:
Merged PR Workflows
Analyze recently merged PRs for change awareness, release notes, and quality signals.Recently Merged Overview
Merged PR Digest
Summarize merged PRs over a time window.TUI Mode Prompt:Headless Mode Prompt:
Release Notes
Generate Release Notes
Turn merged PRs into crisp release notes.TUI Mode Prompt:Headless Mode Prompt:
Deep Dives
Summarize a PR
Get a human-readable summary of a recently merged PR with active discussion.TUI Mode Prompt:Headless Mode Prompt:
Automate with GitHub Actions
Run headless commands on a schedule or in PRs to keep teams informed.Add GitHub Secrets
Repository Settings → Secrets and variables → Actions:CONTINUE_API_KEY
: From hub.continue.dev/settings/api-keysGITHUB_TOKEN
: A token with permissions to read issues/PRs and post comments
Example Workflow
Create.github/workflows/github-mcp-reports.yml
:
Use
continuedev/github-manager-ai
consistently throughout your automation as the recommended agent configuration.Troubleshooting
- Missing or invalid token: Ensure
GITHUB_TOKEN
is set and has the required scopes. Try a minimal test: “List 3 open issues in this repo”. - Permissions errors on comment: Your token must include
public_repo
(public) orrepo
(private) to write comments. - Rate limiting: Reduce frequency or filter queries; consider using a PAT distinct from the default Actions token when running in CI.
- MCP connection timeout: If using custom YAML, increase
connectionTimeout
or verify thecommand
/args
from the Hub listing.
What You’ve Built
After completing this guide, you have a complete AI-powered GitHub workflow system that:- ✅ Uses natural language — Simple prompts for complex GitHub operations
- ✅ Automates issue triage — AI analyzes and summarizes open issues
- ✅ Generates release notes — Automatic PR digests and changelogs
- ✅ Runs continuously — Automated reports via GitHub Actions
Continuous AI
Your GitHub workflow now operates at Level 2 Continuous
AI -
AI handles routine issue triage and PR summaries with human oversight
through review and approval.
Next Steps
- Explore your issues - Try the issue triage prompts on your repository
- Generate release notes - Use the merged PR prompts to create changelogs
- Set up automation - Add the GitHub Actions workflow to your repo
- Customize prompts - Tailor the prompts to your team’s workflow
- Monitor progress - Track issue resolution metrics over time