-
Notifications
You must be signed in to change notification settings - Fork 46
Open
wso2/apim-apps
#1255Labels
Description
Description
The following issues have been identified and need to be fixed for the MCP feature of API Manager 4.6.0
- MCP from an API proxy
- Capabilities are not properly returned
- Only the supported methods have been handled by default, hence some routine method calls fail when 3rd party clients call the server.
- The Auth path with 3rd party client is failing when the auth header is not provided and client tries to generate the token from the application.
- MCP proxy
- Capabilities are not properly returned
- Only the supported methods have been handled by default, hence some routine method calls fail when 3rd party clients call the server.
- The Auth path with 3rd party client is failing when the auth header is not provided and client tries to generate the token from the application.
Steps to Reproduce
- Create an MCP from an API and an MCP from a MCP server.
- Try to invoke it via a 3rd party client (VS Code)
Version
4.6.0, master
Environment Details (with versions)
No response
Reactions are currently unavailable