MC1391947 High
Microsoft Copilot Studio - Use MCP-compliant tools in agent workflows
Summary AI-generated
Microsoft Copilot Studio agent workflows can now use Model Context Protocol (MCP)-compliant tools and knowledge servers as workflow steps, available GA July 15, 2026.
Written by Azure OpenAI (gpt-4.1) from the text of the post below. It can be incomplete or wrong; the original post is authoritative.
Similar posts
Search for more like this- MC1471573 Copilot Studio - Use MCP-compliant tools in agent workflows
- MC1403399 Microsoft Copilot Studio - Create agents optimized for Microsoft 365 and Microsoft 365 Copilot users
- MC1442234 Microsoft Copilot Studio - New workflows designer
- MC1442981 Microsoft Copilot Studio - Invoke agents as workflow steps with the agent node
- MC1323229 Microsoft Copilot Studio - Automate web and desktop apps with computer use
- MC1169071 (Updated) Microsoft 365 Copilot: MCP-based agents now available in Copilot and Microsoft 365 admin center
Original post from Microsoft
We are announcing the ability to use Model Context Protocol (MCP)-compliant tools in agent workflows in Microsoft Copilot Studio. This feature will reach general availability on July 15, 2026.
How does this affect me?
MCP support allows agent workflows to discover and invoke MCP‑compliant tools and knowledge servers as workflow steps.
Agent workflows can pass structured inputs to MCP tools and consume structured outputs downstream, enabling deterministic orchestration around extensible agent capabilities. This functionality makes it possible to use the same MCP server across multiple agents and workflows, align with emerging agent standards, and avoid bespoke connector development for every system.
What action do I need to take?
This message is for awareness, and no action is required.
If you would like more information on this feature, please visit Use MCP-compliant tools in agent workflows.
How does this affect me?
MCP support allows agent workflows to discover and invoke MCP‑compliant tools and knowledge servers as workflow steps.
Agent workflows can pass structured inputs to MCP tools and consume structured outputs downstream, enabling deterministic orchestration around extensible agent capabilities. This functionality makes it possible to use the same MCP server across multiple agents and workflows, align with emerging agent standards, and avoid bespoke connector development for every system.
What action do I need to take?
This message is for awareness, and no action is required.
If you would like more information on this feature, please visit Use MCP-compliant tools in agent workflows.