Category
stayInformed
Severity
normal
Major change
False
Last modified
2026-06-15 12:41:18
Summary source
Azure OpenAI (gpt-4.1)
Action by (Graph)
—
Action by (AI)
2026-07-15 00:00:00
Services
Microsoft Copilot (Power Platform)
Tags
New feature
Master tags
User, Admin, Copilot License
Roadmap IDs
One-line summary
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.
Similar updates
More like thisMC1190188 Microsoft Copilot Studio – Increase sense of security for makers inside Copilot Studio
MC1194567 Power Platform Monitor - Announcing Copilot Studio agent health metrics and alerts in Public Preview
MC1129126 (Updated) Use Microsoft Copilot in Word to create, edit, and transform content directly from chat
MC1191203 Power Platform inventory to include agents, apps, and workflows from Microsoft 365 Copilot, agent flows, and cloud flows
MC1188232 Power Automate - Information regarding the end of support for Document Automation Toolkit
MC1198705 Microsoft 365 Copilot: Nine new connectors now generally available
Details
Body (from Message Center)
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.
Raw JSON (for debugging)
Expand/collapse the full payload below.
Show/hide raw
{
"snapshot_item": {
"action_required_by": null,
"ai_action_required_by": "2026-07-15T00:00:00Z",
"ai_actions": [],
"ai_master_tags": [
"User",
"Admin",
"Copilot License"
],
"ai_model": "gpt-4.1",
"ai_summary": "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.",
"ai_topics": [
"Copilot (power Platform)",
"Copilot Studio"
],
"category": "stayInformed",
"details_map": {},
"id": "MC1391947",
"importance": 4,
"is_major_change": false,
"last_modified": "2026-06-15T12:41:18Z",
"ms_products": [
"Copilot (power Platform)"
],
"platforms": null,
"roadmap_ids": [],
"services": [
"Microsoft Copilot (Power Platform)"
],
"severity": "normal",
"tags": [
"New feature"
],
"title": "Microsoft Copilot Studio - Use MCP-compliant tools in agent workflows"
}
}