You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When configuring an MCP service in Higress via the MCP plugin, if the HTTP response status code of the corresponding API is not equal to 200, the current response is fixed as: call failed, status: %d, response: %s. This error message cannot be customized, and in scenarios where the error code and message are provided through HTTP headers, this information is discarded.
How could it be?
It is recommended to add an error template in the MCP plugin configuration, which provides variables to read header values based on header keys and parse the body as JSON, so that customized error messages can be displayed.
The text was updated successfully, but these errors were encountered:
zhangjingcn
changed the title
The MCP plugin adds an API error response template <ErrorResponseTemplate>
The MCP plugin needs to add an API error response template <ErrorResponseTemplate>
May 27, 2025
Uh oh!
There was an error while loading. Please reload this page.
Why do you need it?
When configuring an MCP service in Higress via the MCP plugin, if the HTTP response status code of the corresponding API is not equal to 200, the current response is fixed as: call failed, status: %d, response: %s. This error message cannot be customized, and in scenarios where the error code and message are provided through HTTP headers, this information is discarded.
How could it be?
It is recommended to add an error template in the MCP plugin configuration, which provides variables to read header values based on header keys and parse the body as JSON, so that customized error messages can be displayed.
The text was updated successfully, but these errors were encountered: