Description
The SDK registry contains the boxmcpserver connector, but SDK 0.14 does not ship a generated typed client for it.
Current state:
ConnectorNames.BoxMCPServer maps to boxmcpserver.ManagedConnectors contains boxmcpserver and its generated usage comment references BoxmcpserverClient.- No
BoxmcpserverExtensions.cs, BoxmcpserverClient, or matching DI registration exists in the package.
This prevents a working Connector Namespace boxmcpserver connection from being consumed through the typed .NET SDK.
Expected
Generate the connector client and models from the managed connector contract, add the corresponding DI registration extension, and include constructor, operation, serialization, and error-response tests.
Context
Found while expanding Azure/Connectors-NET-Samples#72 to cover authenticated Connector Namespace clients end to end.
Authored with Dobby.
Description
The SDK registry contains the
boxmcpserverconnector, but SDK 0.14 does not ship a generated typed client for it.Current state:
ConnectorNames.BoxMCPServermaps toboxmcpserver.ManagedConnectorscontainsboxmcpserverand its generated usage comment referencesBoxmcpserverClient.BoxmcpserverExtensions.cs,BoxmcpserverClient, or matching DI registration exists in the package.This prevents a working Connector Namespace
boxmcpserverconnection from being consumed through the typed .NET SDK.Expected
Generate the connector client and models from the managed connector contract, add the corresponding DI registration extension, and include constructor, operation, serialization, and error-response tests.
Context
Found while expanding Azure/Connectors-NET-Samples#72 to cover authenticated Connector Namespace clients end to end.
Authored with Dobby.