[Parent] Modernize MCP documentation and tooling for toolsets adoption

[github-actions]

Summary

Discussion #5011 spawned a cluster of MCP improvements that all target the same goal: help workflow authors embrace toolsets: as the modern configuration model. This parent issue groups the doc, CLI, and compiler work so we can track remaining gaps from one place.

Goals

• Give authors a single discovery hub that showcases every shared MCP template and toolset capability
• Update reference/tutorial content so toolsets: is the default guidance (with clear migration help)
• Improve CLI help text so MCP commands explain usage patterns and examples
• Add compiler linting that warns when legacy allowed: patterns are still in use

Checklist

• [task] Create interactive MCP explorer documentation #5022 Create an interactive MCP explorer documentation page so the 19 shared templates are easy to browse
• [task] Enhance MCP CLI help text and examples #5020 Expand MCP CLI help/usage text across the five mcp subcommands, with examples and output notes
• [task] Migrate documentation to recommend toolsets over allowed #5019 Rewrite MCP documentation to recommend toolsets: over allowed: and document the migration path
• [task] Create comprehensive "Getting Started with MCP" guide #5018 Publish a comprehensive "Getting Started with MCP" guide that consolidates onboarding content
• [task] Add MCP configuration linter for legacy patterns #5021 Add an MCP configuration linter that flags legacy allowed: patterns and suggests toolset replacements

Notes

• When these land, remember to run make recompile so newly formatted examples stay in sync with compiled workflows.
• Future MCP work items that reinforce toolset adoption can be added here to keep visibility high.

AI generated by Issue Arborist