PR Checklist

Please check to confirm your PR fulfills the following requirements:

• The commit message follows our guidelines:https://github.com/angular/angular-cli/blob/main/CONTRIBUTING.md#-commit-message-guidelines
• Tests for the changes have been added (for bug fixes / features)
  • I couldn't find any existing MCP-related tests to update. I've used@modelcontextprotocol/inspector to test the feature.
• Docs have been added / updated (for bug fixes / features)
  • I couldn't find any existing MCP-related doc to update

PR Type

What kind of change does this PR introduce?

• Bugfix
• Feature
• Code style update (formatting, local variables)
• Refactoring (no functional changes, no api changes)
• Build related changes
• CI related changes
• Documentation content changes
• Other... Please describe:

What is the current behavior?

No MCP tool to provide Angular update guidance.

What is the new behavior?

This PR introduces theupdate_guide MCP tool that provides the same update info as onhttps://angular.dev/update-guide but in a convenient way to be used by LLMs.

Does this PR introduce a breaking change?

• Yes
• No

Other information

Therecommendations.ts is directly copied fromhttps://github.com/angular/angular/blob/main/adev/src/app/features/update/recommendations.ts

I think a sync mechanism should be implemented, or the website could provide a JSON format that could loaded dynamically. I'm all open for suggestions regarding this, to make sure these files are synced.
Simplest idea I have: add a basiccurl that fetches the files before building.

Also, regarding thewindows parameter, I used Node.js platform detection to automatically infer it, but let me know if you would prefer to still have it as an option of the tool.