From Log Line to Merged Fix: AI SRE Agent AURA with GitHub MCP

Mezmo

Aug 13, 2026

Knowing why it broke is not the same as having it repaired. Point the agent at the repos behind the service and the change comes back as a pull request.

Learn more about AURA → https://www.mezmo.com/aura
Get started today → https://github.com/mezmo/aura
Get deployment help → https://www.mezmo.com/contact

A Govee integration crash-loops under Home Assistant because the container cannot write to a directory it does not own. That much was already established: the previous homelab video stopped at the root cause on purpose, so the next pass could improve the agent's configuration first.

Three changes go into that config. An environment section tells AURA up front that this is a homelab running Docker Compose, along with where observability data lands, which cuts the discovery work it would otherwise spend tokens on. The GitHub MCP server is added with a personal access token scoped to read access across the organization's repositories, plus administration read so the tools can discover what is there. Each worker then gets an explicit, reduced list of MCP tools rather than the full set, with the Grafana log and metrics tools split across the workers that need them.

Given the same prompt, AURA reaches the same root cause. With the repositories in scope it goes further: it finds the Compose file behind Home Assistant and the Govee bridge, follows it to the user the container is declared to run as, and identifies the mismatch against the host directory. It does not reach the public repository on its own, and the video shows the follow-up prompt rather than editing around it.

The recommendation is to stop depending on host file system ownership and convert the bind mount to a Docker named volume. AURA does not write that change. It files a GitHub issue behind an approval gate, documented with the problem, the root cause, and the proposed fixes, and Claude opens the pull request from it. The diff is reviewed and merged by hand. AURA then re-runs the original check and confirms the change is merged and the service is healthy, without anyone logging into the host.

AURA is built for SREs and homelab operators who want an agent that reads the code behind the services it investigates and produces something a repository can act on.

Chapters

0:00 Where the last investigation left off

0:44 Adding repository access to the config

2:15 The GitHub MCP server and its token scopes

2:52 A GitHub analyst worker with a reduced tool list

3:27 An approval gate on issue creation

3:39 Splitting the Grafana tools across workers

4:02 The same prompt, the same root cause

5:17 A deeper dive with the repositories in scope

7:04 The declared container user and the UID mismatch

8:11 Writing the issue instead of the code

9:52 Claude opens the pull request