[satyajeetjadhav]

Looks interesting. In my experience the way current coding agents behave is - they make a change, then rely on linter to highlight errors due to the change. Once linter errors are highlighted, they try to fix them.

Providing access to something like this via mcp might help these coding agents plan better and limit or atleast understand the blast radius for refactors.

Will try.

[srijanshukla18]

You've hit the nail on the head! "Understanding the blast radius" is the core problem xray mcp tries to solve.

The whole idea behind tools like what_breaks is to give the agent that foresight before it makes a change, moving it from a reactive "change -> lint -> fix" cycle to a more proactive "plan -> analyze -> change" workflow.

Thanks for checking it out!

About the linting use case specifically, I've found claude code hooks to be very beneficial. Not sure if other tools have an equivalent. Check that out too!