Description
When an MCP server is proxied through WSO2 APIM, the Publisher Portal does not reflect tools added to the backend MCP server after the API was initially imported. The tool list shown in the Publisher is a static snapshot captured at import time. There is no refresh/sync mechanism available to pull the latest tool definitions from the live backend without re-importing the API as a new MCP proxy.
Steps to Reproduce
- Create a mock MCP backend server with one initial tool (get_user)
- Create an MCP API in APIM Publisher pointing to the created MCP the endpoint and confirm created tool (get_user) appears in the Publisher Portal
- Add a new tool to the backend MCP:
- Go to the Publisher Portal and open the MCP API and verify the created new tool is not listed.
Version
APIM 4.6.0
Environment Details (with versions)
No response
Description
When an MCP server is proxied through WSO2 APIM, the Publisher Portal does not reflect tools added to the backend MCP server after the API was initially imported. The tool list shown in the Publisher is a static snapshot captured at import time. There is no refresh/sync mechanism available to pull the latest tool definitions from the live backend without re-importing the API as a new MCP proxy.
Steps to Reproduce
Version
APIM 4.6.0
Environment Details (with versions)
No response