Using an MCP Server to Fix Tests that Failed on CI


We just shipped an MCP Server via the RWX CLI.
Upgrade to at least version 1.11, and it'll be available via rwx mcp serve.
$ brew upgrade rwx-cloud/tap/rwx$ rwx --versionrwx version v1.11.0
MCP Tool to Get Test Failures
With RWX, test results are a semantic output. Rather than having to scroll through logs, you can easily see which tests failed in the UI. And now, AI can easily see which tests failed via an MCP tool.
Claude, fix the tests that failed in this CI run
Add RWX to Claude's MCP configuration:
$ claude mcp add rwx -- rwx mcp serve
You can then see it in the list of servers:
$ claude mcp listChecking MCP server health...rwx: rwx mcp serve - ✓ Connected
Here's a snippet from a Claude session that gets a list of tests that failed and fixes them.
> fix the test failures from this run:https://cloud.rwx.com/mint/rwx/runs/df4781e384584db98c3274a84f2bcfc2⏺ I'll help you fix the test failures from that RWX run. Let me firstget the details of the failed tests.⏺ rwx - get_run_test_failures (MCP)(run_urls:["https://cloud.rwx.com/mint/rwx/runs/df4781e384584db98c3274a84f2bcfc2"])⎿ Failed tests:- src/calculator.test.ts… +2 lines (ctrl+r to expand)⏺ Now let me examine the test file and the implementation to understandwhat's failing.
Demo
Never miss an update.
Get the latest releases and news about RWX and our ecosystem with our newsletter.
Related posts

May 18, 2026
RWX now supports Codeberg and Forgejo
RWX now supports Codeberg and self-hosted Forgejo repositories, giving teams a reliable CI/CD path outside GitHub.

May 13, 2026
Why the TanStack supply chain attack can't happen on RWX
The TanStack npm compromise hinged on GitHub Actions cache poisoning. RWX's content-based caching and branch-locked vaults make that attack structurally impossible.