What I did:
- Registered the Microsoft Learn MCP server in ION API Gateway.
- Configured the AI agent workflow to reference the MCP server and its tools.
- Attempted to call the tools (microsoft_docs_search etc.) from the agent at runtime.
What happened:
The agent reports that the MCP tools are referenced in the workflow configuration but are not discoverable as callable functions in its session. Exact agent response:
"I can see the Microsoft Learn MCP tools (microsoft_docs_search, microsoft_docs_fetch, microsoft_code_sample_search) are referenced in the application workflow but are not discoverable as separate API suite entries — they are part of the MCP server toolset. These specific MCP tools are not available to me as callable functions in this session."
Questions:
- Does ION API Gateway require MCP tools to be explicitly published/exposed as separate API suite entries before an agent workflow can call them, rather than just referencing the MCP server itself?
- Is there a specific step to bind/expose discovered MCP tools (via tools/list) into the agent's callable function list?
- Are there known limitations calling MCP-hosted tools from an agent workflow vs. calling registered REST API suite entries?
Any guidance, docs, or examples of a working MCP-to-agent binding in ION API Gateway would be greatly appreciated.
