mcp-github·integration·active

GitHub MCP

Reads PRs, issues, code search; opens PRs containing EVAN-generated automation, SARA remediation patches, and ARIA-recommended changes.

EVAN SARA ARIAtrigger · mcp⌘ MCP · GitHub

GitHub MCP

Reads PRs, issues, and code search; opens PRs containing EVAN-generated automation, SARA remediation patches, and ARIA-recommended changes.

What flows in

·Repo metadata (default branch, protected branches, CODEOWNERS)

·Pull request status, reviewers, checks

·Issues, including label state and assignee

·Code search results (used by EVAN for finding existing patterns)

·Commit history (used byTrend Detector for cross-referencing changes with sprint events)

What flows out

·New branches with EVAN-generated tests

·New branches with SARA remediation diffs

·Pull requests with full bodies (including evidence links)

·Issue comments on PRs (e.g. CI fail explanations)

·Status checks (custom checks reporting agent verdicts)

Authentication

GitHub App preferred over PATs. The app is scoped per-org with:

·pull_requests: write

·contents: write (only on the branches it creates)

·issues: write

·checks: write

→The app never modifies main / default branches directly. All writes go through PRs that follow the org's protection rules.

CODEOWNERS awareness

When opening a PR, the connector reads CODEOWNERS and:

·Auto-requests reviews from the right teams

·Avoids opening PRs that no human can review (e.g. against a path with no owner)

·Tags PRs with the owning team's label

PR body conventions

Generated PR bodies follow a strict template:

·What — the change in one sentence

·Why — link to the agent finding or recommendation

·Evidence — link toEvidence Capture for SARA, run report for EVAN

·Risk — low / medium / high based on touched paths

·How to verify — the regression test that proves the fix

→The "How to verify" section is non-negotiable. PRs from agents that don't include it are auto-flagged.

Code search for context

Before generating code, EVAN uses GitHub code search to find:

·Existing patterns in the repo (so generated code matches style)

·Reused utilities (so generated code doesn't duplicate them)

·Test conventions (so generated tests live in the right place)

This is what keeps EVAN-generated code from looking like a foreign object in the codebase.

Server

mcp://api.github.com/mcp

Vendor

GitHub.

Enterprise support

For GHE Server, the connector supports custom hostnames and self-signed certificates. Configuration is per-installation.

MCP server endpoint

mcp://api.github.com/mcp

vendor · GitHub

Related · integration

Sprint Context Loader

sprint-context-loader

Pulls sprint metadata — name, dates, team, release tag, prior trend data — directly from connected issue trackers via MCP.

Jira MCP

mcp-jira

Bidirectional Jira connector. TARA pulls stories from sprints; ARIA pushes findings, recommendations, and quality reports back as issues, comments, or sprint reviews.

TestRail MCP

mcp-testrail

Pulls existing test cases and execution history; pushes EVAN-generated tests and run results back as cases, runs, and milestone reports.

Azure DevOps MCP

mcp-ado

Pulls work items + repos; pushes test plans, suites, and runs. Handles ADO test points and outcome states with full bi-directional sync.

Confluence MCP

mcp-confluence

Reads PRDs and ACs from Confluence pages as TARA input. Publishes ARIA's quality reports back as Confluence pages with embedded charts.

Slack MCP

mcp-slack

Real-time notifications when SARA finds Critical issues, LEO breaches an SLO, or ARIA's trend detector flags a regression. Routed to the right channel by component.