Share via


Troubleshooting Model Context Protocol (MCP) integration

This article provides troubleshooting guidance for integrating your agent with Model Context Protocol (MCP) servers.

Known issues and workarounds

The following are identified issues the product team is aware of and working on:

Issues Resolution/Workaround
Currently, the endpoint returned in the Open SSE connection call must be a full URI. Not applicable.
A System.FormatException is thrown when the exclusiveMinimum property is set to an integer (instead of a Boolean) in the MCP tool definition input schema. Not applicable.
The MCP tool definition input schema definition is truncated when a type in a tool definition is an array of multiple types instead of a single type. Make the values for type fields a single type.
Tools with reference type inputs in the schema are filtered from the list of available tools for MCP server. Reference type inputs and outputs aren't supported. Not applicable.
Tools with enum type inputs in the schema are interpreted as string instead of enum. Not applicable.