Server startup always loads all tool assemblies

[hallipr]

Our server startup currently has Program.cs statically loading the setup classes from every tool assembly:

internal class Program
{
    private static IAreaSetup[] Areas = RegisterAreas();

    private static IAreaSetup[] RegisterAreas()
    {

        return [
            // Register core areas
            new Azure.Mcp.Tools.AzureBestPractices.AzureBestPracticesSetup(),
            new Azure.Mcp.Tools.Extension.ExtensionSetup(),

            // Register Azure service areas
            new Azure.Mcp.Tools.Aks.AksSetup(),
            new Azure.Mcp.Tools.AppConfig.AppConfigSetup(),
            new Azure.Mcp.Tools.AppLens.AppLensSetup(),
...

This means that every process start, even for calls like azmcp --help or azmcp --version load at least 53 assemblies.

This causes time to first message to be ~15 seconds on a single run and >60 seconds when processes are started concurrently.

Refactoring app startup to delay tool assembly loading until that tool is being invoked would greatly improve single command calls and metadata calls like --help and --version.

This requires making command metadata available to the server without having the tool assembly loaded. That would require either moving the command definition out of the tool assembly or source generating enough command definition to support server startup, mcp tool listing and --help calls from the server assembly without pre-loading the tool assemblies.

[github-actions]

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @alzimmermsft @anannya03 @anuchandy @g2vinay @microsoft/azure-mcp @xiangyan99.