Make MCP client initialization timeout configurable via ToolOptions

[Grant Harris (gwharris7)]

Summary

• Add nullable McpClientInitializationTimeoutSeconds property to ToolOptions so consumers can override the MCP client initialization timeout
• When not set (null), the MCP SDK default (60s) is used — no behavioral change for existing consumers
• When set, both McpClientOptions.InitializationTimeout and HttpClient.Timeout are configured to match

Motivation

Consumers connecting to the MCP platform may experience OperationCanceledException when downstream dependencies are slow. The MCP SDK's default 60-second initialization timeout is not configurable through ToolOptions, leaving no way for consumers to adjust it for their agents.

Usage

// Default behavior — no change needed, SDK default timeout applies
var options = new ToolOptions();
await configService.GetMcpClientToolsAsync(turnContext, serverConfig, token, options);

// Custom timeout for slow environments
var options = new ToolOptions
{
    McpClientInitializationTimeoutSeconds = 180 // 3 minutes
};
await configService.GetMcpClientToolsAsync(turnContext, serverConfig, token, options);

Changes

• src/Tooling/Core/Models/ToolOptions.cs — Add int? McpClientInitializationTimeoutSeconds property
• src/Tooling/Core/Services/McpToolServerConfigurationService.cs — Apply timeout only when explicitly set

Test plan

• Verified default behavior (null) uses MCP SDK default timeout
• Verified explicit value is applied to both McpClientOptions.InitializationTimeout and HttpClient.Timeout
• Built and tested end-to-end with sample-agent against MCP platform

---

Replaces #212 (fork PR could not trigger CodeQL default setup)
Original approvals: Sellakumaran Kanagarathnam (@sellakumaran) ajmfehr

[github-actions]

⚠️ Deprecation Warning: The deny-licenses option is deprecated for possible removal in the next major release. For more information, see issue 997.

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

Scanned Files

None

[Grant Harris (gwharris7)]

No longer needed — PR #212 was merged successfully.

[Copilot]

Pull request overview

This PR adds an opt-in configuration surface on ToolOptions that allows consumers to override the MCP client initialization timeout, and wires that value through to MCP client creation so slow downstream dependencies don’t cause premature initialization cancellations.

Changes:

• Added ToolOptions.McpClientInitializationTimeoutSeconds (int?) to allow overriding the MCP SDK’s initialization timeout while preserving default behavior when unset.
• Applied the configured timeout (when set) to both McpClientOptions.InitializationTimeout and the HttpClient.Timeout used by the SSE transport.
• Added unit tests covering default/null behavior, validation bounds, and timeout conversion logic.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.

File	Description
src/Tooling/Core/Services/McpToolServerConfigurationService.cs	Validates and applies an optional initialization timeout during MCP client creation; adds helper to validate/convert seconds to TimeSpan?.
src/Tooling/Core/Models/ToolOptions.cs	Introduces a nullable McpClientInitializationTimeoutSeconds option with XML documentation.
src/Tests/Microsoft.Agents.A365.Tooling.Tests/Services/McpClientInitializationTimeoutTests.cs	Adds unit tests for the new option and validation helper.