Summary
The foundry-mcp server entry in plugin/.mcp.json should be removed because Foundry MCP tools are now proxied through the azure MCP server (@azure/mcp). Having a separate foundry-mcp entry is redundant.
What to change
1. Remove foundry-mcp from plugin/.mcp.json
Delete this block:
"foundry-mcp": {
"type": "http",
"url": "https://mcp.ai.azure.com"
}
2. Update test assertion
tests/microsoft-foundry/foundry-agent/observe/unit.test.ts line ~74 asserts foundry-mcp appears in the observe content. Update to check for azure instead.
Why
Foundry tools are now available through the unified @azure/mcp server, so a dedicated foundry-mcp HTTP entry is no longer needed.
Summary
The
foundry-mcpserver entry inplugin/.mcp.jsonshould be removed because Foundry MCP tools are now proxied through theazureMCP server (@azure/mcp). Having a separatefoundry-mcpentry is redundant.What to change
1. Remove
foundry-mcpfromplugin/.mcp.jsonDelete this block:
2. Update test assertion
tests/microsoft-foundry/foundry-agent/observe/unit.test.tsline ~74 assertsfoundry-mcpappears in the observe content. Update to check forazureinstead.Why
Foundry tools are now available through the unified
@azure/mcpserver, so a dedicatedfoundry-mcpHTTP entry is no longer needed.