GitHub Integration

DevBoy tools provides full integration with GitHub for managing issues, pull requests, and code reviews through AI assistants.

Quick Config Generator

Required token scopes

When creating a GitHub personal access token, you need to select the following scopes:

ScopeDescriptionRequired For
repoFull repository accessReading issues, PRs, diffs; creating comments
read:userRead user informationIdentifying the current user

Configuration

Basic configuration

# Set repository owner (user or organization)
devboy config set github.owner <owner>

# Set repository name
devboy config set github.repo <repo>

# Store token in OS keychain
devboy config set-secret github.token <token>

Configuration file

Settings are stored in ~/.config/devboy-tools/config.toml:

[github]
owner = "meteora-pro"
repo = "devboy-tools"

The token is stored separately in the OS keychain for security.

MCP tools

Once configured, the following MCP tools are available:

Issue tools

ToolDescription
get_issuesList issues with filters (state, labels, assignee)
get_issueGet a single issue by key (e.g., "gh#123")
get_issue_commentsGet all comments for an issue
create_issueCreate a new issue
update_issueUpdate an existing issue
add_issue_commentAdd a comment to an issue

Pull request tools

ToolDescription
get_merge_requestsList PRs with filters
get_merge_requestGet a single PR by key (e.g., "pr#123")
get_merge_request_discussionsGet code review discussions
get_merge_request_diffsGet file diffs for a PR
create_merge_requestCreate a new pull request
create_merge_request_commentAdd a comment (general or inline)

Output formats

All tools support three output formats via the format parameter:

  • markdown (default) - Human-readable with formatting
  • compact - Condensed format for limited context
  • json - Raw JSON data

Example:

{
  "key": "gh#123",
  "format": "json"
}

Testing

Verify your GitHub configuration:

devboy test github

This will test the connection and display your GitHub user information.

Troubleshooting

"Bad credentials" error

  • Verify your token is copied correctly
  • Check that the token hasn't expired
  • Ensure the token has the required repo scope

"Not Found" error

  • Verify the owner and repo names are correct
  • Ensure the repository exists and is accessible
  • Check that your token has access to the repository

Rate limiting

GitHub API has rate limits:

  • 5,000 requests per hour for authenticated users
  • The tool will show a rate limit error if exceeded