MC1471573 Low
Copilot Studio - Use MCP-compliant tools in agent workflows
Summary AI-generated
Microsoft Copilot Studio now supports integrating MCP-compliant tools into agent workflows for enhanced orchestration and extensibility. General availability started 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- MC1391947 Microsoft Copilot Studio - Use MCP-compliant tools in agent workflows
- MC1403399 Microsoft Copilot Studio - Create agents optimized for Microsoft 365 and Microsoft 365 Copilot users
- MC1323229 Microsoft Copilot Studio - Automate web and desktop apps with computer use
- MC1442234 Microsoft Copilot Studio - New workflows designer
- MC1218332 Power Platform - Track, manage and scale Copilot adoption in PPAC new functionality
- MC1442981 Microsoft Copilot Studio - Invoke agents as workflow steps with the agent node
Original post from Microsoft
We are announcing the ability to use MCP (model context protocol) - compliant tools in agent workflows in Microsoft Copilot Studio. This feature reached general availability on July 15, 2026.
How does this affect me?
How does this affect me? This feature allows users to integrate proprietary systems, dynamic knowledge sources, and custom actions into agentic workflows with MCP support. Agent workflows can pass structured inputs to MCP-compliant tools and consume structured outputs downstream, enabling deterministic orchestration around agent-extensible capabilities. This functionality allows usage of the same MCP server across multiple agents and workflows, avoiding bespoke connector development for every system.
MCP tools execute under existing workflow governance, monitoring, and lifecycle management.
What action do I need to take?
This message is for awareness, and no action is required.
How does this affect me?
How does this affect me? This feature allows users to integrate proprietary systems, dynamic knowledge sources, and custom actions into agentic workflows with MCP support. Agent workflows can pass structured inputs to MCP-compliant tools and consume structured outputs downstream, enabling deterministic orchestration around agent-extensible capabilities. This functionality allows usage of the same MCP server across multiple agents and workflows, avoiding bespoke connector development for every system.
MCP tools execute under existing workflow governance, monitoring, and lifecycle management.
What action do I need to take?
This message is for awareness, and no action is required.