Tool for retrieving workflow status and logs

[C-Ross]

Describe the feature or problem you’d like to solve

Agents are great at researching and automatically resolving job failures, however currently the agent can only read this data via gh run view or gh api command line tools, slowing iteration and making a much noisier experience for developers.

This also creates permission mismatch issues if the token in the environment is different than the one given to the MCP server.

ex: gh run view 20656271469 --log --repo my_org/my_repo 2>&1 | tail -200

gh api repos/my_org/my_repo/actions/runs/20656271469/jobs --jq '.jobs[] | select(.id == 59317655947) | {name: .name, conclusion: .conclusion, steps: [.steps[] | {name: .name, conclusion: .conclusion}]}'

Proposed solution

Provide a tool for accessing Actions workflows state and logs. Being able to rerun or invoke additional workflows would likely be a good followup, but these writes should be permissioned differently.

Example prompts or workflows (for tools/toolsets only)

Investigate failures of #.github/workflow/xyz, determine a cause and propose a solution.

Investigate failures of the Build and Test workflow, and find the change that introduced the failure.

Build and Test seems flaky, analyze how often it has been rerun and succeeded on the same commit, then investigate whcih tests contributed to those failures.

Additional context

Will provide on request.

[mattdholloway]

We already support this via the get_job_logs tool within the actions toolset. This is not enabled by default, so will need to be enabled.

The documentation for enabling other toolsets can be found in the following locations:

• Remote MCP Docs
• Local MCP Docs

Although we currently support two different versions of the toolset controlled under a feature flag, this tool will remain the same either way.

[C-Ross]

This already exists as a toolset.