Correctly read url parameter of ToolingManifest.json when the file is read from disk.

[adner]

ParseServerConfigFromManifest does not currently read the url property of the ToolingManifest.json file, instead it defaults to a base url that only works for first-party Agent 365 tools.

When using the A365 MCP Management MCP Server to create custom MCP Servers, the URL of such a server needs to be configured in the ToolingManifest.json file. Example:

{
  "mcpServers": [
    {
      "mcpServerName": "mcp_MailTools",
      "mcpServerUniqueName": "mcp_MailTools"
    }
...
    {
      "mcpServerName": "adde_mycoolmcpserver",
      "mcpServerUniqueName": "adde_mycoolmcpserver",
      "scope": "McpServers.DataverseCustom.All",
      "url": "https://agent365.svc.cloud.microsoft/mcp/environments/f828e740-6703-e4e7-b631-11a48500a013/servers/adde_mycoolmcpserver"
    }
  ]
}

This PR fixes this, and also aligns the code in ParseServerConfigFromManifest with ParseServerConfig.

[adner]

@microsoft-github-policy-service agree [company="{your company}"]

@microsoft-github-policy-service agree

[Copilot]

Pull request overview

This PR fixes ParseServerConfigFromManifest to correctly read the url parameter from ToolingManifest.json files, enabling custom MCP server URLs to be configured. Previously, the method only supported first-party Agent 365 tools by defaulting to a base URL. The changes align the manifest parsing logic with the existing ParseServerConfig method.

Key Changes:

• Added parsing of the url property from ToolingManifest.json
• Added fallback logic to read mcpServerUniqueName when mcpServerName is not present
• Modified URL construction to use provided URL or fall back to building one from the server name