Summary
Unit 6 of 6 · Module 9: Integrate MCP Tools with Azure AI Agents
Read this lesson
Module 9 in snow globes
That's Module 9: MCP tools for Foundry Agent Service. Here's the shelf of snow globes from the trip. From the perfumery: hand-wiring every tool doesn't scale, so an MCP server keeps them in one catalog. From the food market: the server is the live menu, any model can read it, and a client turns each tool into a function wrapper for the agent. From the circus: FastMCP and the mcp tool decorator build the server, while list tools and call tool are the client's side. From the film backlot: with the MCP tool, the agent service connects for you, with allowed tools, headers, and approvals. And from the warehouse: you approved each call in a loop, then wired your own inventory server to an agent.
Where next
So by connecting your agent to an MCP server, you discover and register tools while the app runs, without hardcoding APIs or redeploying your agent. The client generates function wrappers from the tools it discovers, and connects them straight to your agent. That lets your agent adapt as its toolset grows, alongside your applications. To go further, read the Model Context Protocol user guide, and the Foundry docs on connecting to MCP servers. Next up: knowledge-enhanced agents with Foundry IQ. Now try the module review quiz below.
Facts from Microsoft's documentation: Connect agents to MCP server endpoints; What is Microsoft Foundry Agent Service? (CC BY 4.0), rewritten in Loop's own words and examples. Narration, animation, and quiz by Loop. Microsoft, Azure, and Microsoft Foundry are trademarks of Microsoft. Loop is independent and not affiliated with or endorsed by Microsoft.