Dashboard & Response Tools

Overview

16 tools for monitoring activity and taking action across GitHub repositories. Useful for maintainers, reviewers, and security responders.

Dashboard Tools (7)

github_dashboard

Comprehensive overview of all GitHub activity.

Parameters: None (uses authenticated user)

Output:

{
  "notifications": {
    "unread": 12,
    "participating": 5,
    "mentions": 2
  },
  "assigned_issues": {
    "open": 8,
    "urgent": 3
  },
  "prs_to_review": {
    "total": 6,
    "waiting_on_you": 4
  },
  "security_alerts": {
    "critical": 2,
    "high": 5,
    "medium": 12
  },
  "failed_workflows": {
    "count": 3,
    "recent": [...]
  },
  "recent_activity": [...]
}

Use case: Morning triage — see everything that needs attention in one view.

github_notifications

List all notifications with filtering.

Parameters:

• all (optional): Include read notifications (default: false)
• participating (optional): Only show conversations you’re involved in
• since (optional): Notifications since date (e.g., “2 days ago”)
• limit (optional): Maximum notifications (default: 50)

Output:

{
  "unread": 12,
  "notifications": [
    {
      "id": "123",
      "type": "PullRequest",
      "repository": "owner/repo",
      "title": "Fix authentication bug",
      "reason": "mention",
      "unread": true,
      "updated_at": "2 hours ago",
      "url": "https://github.com/owner/repo/pull/42"
    }
  ]
}

github_mark_notification_read

Mark notification as read.

Parameters:

• notification_id (required): Notification ID (from github_notifications)

Example:

{
  "notification_id": "123"
}

github_assigned_issues

Issues assigned to you across all repositories.

Parameters:

• state (optional): open, closed, or all (default: open)
• sort (optional): created, updated, comments (default: created)
• limit (optional): Maximum issues (default: 30)

Output:

{
  "total": 8,
  "issues": [
    {
      "number": 123,
      "title": "Database connection timeout",
      "repository": "owner/repo",
      "state": "open",
      "labels": ["bug", "priority-high"],
      "comments": 5,
      "created_at": "3 days ago",
      "url": "https://github.com/owner/repo/issues/123"
    }
  ]
}

github_prs_to_review

Pull requests waiting for your review.

Parameters:

• state (optional): open, closed, or all (default: open)
• limit (optional): Maximum PRs (default: 30)

Output:

{
  "total": 6,
  "prs": [
    {
      "number": 456,
      "title": "Refactor authentication module",
      "repository": "owner/repo",
      "author": "contributor",
      "draft": false,
      "requested_reviewer": true,
      "created_at": "1 day ago",
      "url": "https://github.com/owner/repo/pull/456"
    }
  ]
}

github_security_alerts

Security alerts across all repositories.

Parameters:

• severity (optional): Filter by critical, high, medium, low
• state (optional): open, dismissed, or all (default: open)
• limit (optional): Maximum alerts (default: 50)

Output:

{
  "total": 19,
  "by_severity": {
    "critical": 2,
    "high": 5,
    "medium": 12,
    "low": 0
  },
  "alerts": [
    {
      "type": "dependabot",
      "severity": "critical",
      "package": "express",
      "vulnerability": "CVE-2024-12345",
      "repository": "owner/repo",
      "created_at": "5 days ago",
      "fix_available": true
    }
  ]
}

github_failed_workflows

Failed GitHub Actions workflows.

Parameters:

• since (optional): Workflows since date (default: “7 days ago”)
• limit (optional): Maximum workflows (default: 20)

Output:

{
  "total": 3,
  "workflows": [
    {
      "name": "CI",
      "repository": "owner/repo",
      "branch": "main",
      "conclusion": "failure",
      "run_number": 123,
      "started_at": "2 hours ago",
      "url": "https://github.com/owner/repo/actions/runs/123",
      "can_rerun": true
    }
  ]
}

Response Tools (3)

github_comment_issue

Add comment to an issue.

Parameters:

• owner (required): Repository owner
• repo (required): Repository name
• issue_number (required): Issue number
• body (required): Comment text (supports Markdown)

Example:

{
  "owner": "facebook",
  "repo": "react",
  "issue_number": 12345,
  "body": "I can reproduce this on React 18.2.0. Here's a minimal example:\n\n```jsx\n// code here\n```"
}

Output:

{
  "comment_id": 789,
  "url": "https://github.com/facebook/react/issues/12345#issuecomment-789",
  "created_at": "just now"
}

github_comment_pr

Add comment to a pull request.

Parameters: Same as github_comment_issue, but with pr_number instead.

Example:

{
  "owner": "nodejs",
  "repo": "node",
  "pr_number": 54321,
  "body": "LGTM! Just one minor suggestion:\n- Consider adding a test for edge case X\n\nOtherwise looks good to merge."
}

github_review_pr

Create pull request review (APPROVE, REQUEST_CHANGES, or COMMENT).

Parameters:

• owner (required): Repository owner
• repo (required): Repository name
• pr_number (required): PR number
• event (required): APPROVE, REQUEST_CHANGES, or COMMENT
• body (optional): Review summary
• comments (optional): Array of line-specific comments

Example — Simple approval:

{
  "owner": "username",
  "repo": "my-project",
  "pr_number": 42,
  "event": "APPROVE",
  "body": "Looks good! Great work on the error handling."
}

Example — Request changes with inline comments:

{
  "owner": "username",
  "repo": "my-project",
  "pr_number": 42,
  "event": "REQUEST_CHANGES",
  "body": "A few issues need to be addressed before merging.",
  "comments": [
    {
      "path": "src/auth.go",
      "position": 23,
      "body": "This should use constant-time comparison to prevent timing attacks."
    },
    {
      "path": "README.md",
      "position": 15,
      "body": "Typo: 'authentification' → 'authentication'"
    }
  ]
}

Output:

{
  "review_id": 999,
  "state": "APPROVED",
  "url": "https://github.com/username/my-project/pull/42#pullrequestreview-999"
}

Repair Tools (6)

Take action to close loops and fix issues.

github_close_issue

Close an issue with optional comment.

Parameters:

• owner (required): Repository owner
• repo (required): Repository name
• issue_number (required): Issue number
• comment (optional): Closing comment

Example:

{
  "owner": "username",
  "repo": "my-project",
  "issue_number": 123,
  "comment": "Fixed in PR #456. Thanks for reporting!"
}

github_merge_pr

Merge pull request.

Parameters:

• owner (required): Repository owner
• repo (required): Repository name
• pr_number (required): PR number
• merge_method (optional): merge, squash, or rebase (default: merge)
• commit_title (optional): Custom merge commit title
• commit_message (optional): Custom merge commit message

Example:

{
  "owner": "username",
  "repo": "my-project",
  "pr_number": 42,
  "merge_method": "squash",
  "commit_title": "feat: Add user authentication (#42)"
}

Merge methods

• merge: Creates merge commit (preserves all commits)
• squash: Combines all commits into one
• rebase: Rebases and fast-forwards (linear history)

Choose based on your project’s merge strategy.

github_rerun_workflow

Re-run failed GitHub Actions workflow.

Parameters:

• owner (required): Repository owner
• repo (required): Repository name
• run_id (required): Workflow run ID (from github_failed_workflows)

Example:

{
  "owner": "username",
  "repo": "my-project",
  "run_id": 123456789
}

Output:

{
  "status": "rerun_triggered",
  "run_id": 123456789,
  "url": "https://github.com/username/my-project/actions/runs/123456789"
}

Security Alert Dismissal (3 tools)

Dismiss security alerts after manual review or acceptance of risk.

github_dismiss_dependabot_alert

Dismiss Dependabot security alert.

Parameters:

• owner (required): Repository owner
• repo (required): Repository name
• alert_number (required): Alert number
• reason (required): fix_started, inaccurate, no_bandwidth, tolerable_risk, not_used
• comment (optional): Explanation

Example:

{
  "owner": "username",
  "repo": "my-project",
  "alert_number": 12,
  "reason": "fix_started",
  "comment": "PR #456 addresses this vulnerability. Will merge tomorrow."
}

github_dismiss_code_alert

Dismiss Code Scanning alert.

Parameters: Similar to Dependabot alert

• reason: false_positive, won't_fix, used_in_tests

github_dismiss_secret_alert

Dismiss Secret Scanning alert.

Parameters: Similar to Dependabot alert

• reason: false_positive, revoked, used_in_tests, won't_fix

Example:

{
  "owner": "username",
  "repo": "my-project",
  "alert_number": 5,
  "reason": "revoked",
  "comment": "Token was rotated and the old one is now invalid."
}

Dismissal accountability

All alert dismissals are logged in GitHub’s audit log. Only dismiss alerts after thorough review.

Common Workflows

Morning Triage

1. "Show me my GitHub dashboard"
   → github_dashboard

2. "What security alerts need attention?"
   → github_security_alerts (severity: critical)

3. "List PRs I need to review"
   → github_prs_to_review

4. "Mark notification 123 as read"
   → github_mark_notification_read

PR Review & Merge

1. "List PRs waiting for my review"
   → github_prs_to_review

2. "Comment on PR #42: 'Looks good overall, minor comments below'"
   → github_comment_pr

3. "Approve PR #42 with review"
   → github_review_pr (event: APPROVE)

4. "Merge PR #42 using squash"
   → github_merge_pr (merge_method: squash)

Fix CI Failure

1. "Show me failed workflows in the last 24 hours"
   → github_failed_workflows (since: "1 day ago")

2. [Identify flaky test]

3. "Re-run workflow 123456789"
   → github_rerun_workflow

Security Alert Handling

1. "Show critical security alerts"
   → github_security_alerts (severity: critical)

2. [Review vulnerability and fix]

3. "Dismiss Dependabot alert #12 as fix started"
   → github_dismiss_dependabot_alert (reason: fix_started)

Responsible use

These tools act on remote issues, pull requests, workflows, and alerts. Confirm repository context and provide clear rationale in comments, reviews, and dismissals. We are not responsible for misuse or resulting damage.

Required Token Scopes

Tool Category	Required Scope
Dashboard, Notifications	notifications (included in repo)
Comments, Reviews	repo
Merge PRs	repo
Rerun Workflows	workflow
Dismiss Security Alerts	security_events

See Security Best Practices → for detailed token configuration.