Agent Loop now includes MCP support—unlocking enterprise data through secure, connector‑driven MCP servers.
At Ignite, we announced that Agent Loop in Azure Logic Apps Standard now supports the Model Context Protocol (MCP), enabling agents to discover and call external tools through an open, standardized interface. This brings powerful, flexible tool extensibility to both conversational and autonomous agents.
MCP support gives agents a common language and secure channel to interact with enterprise systems. By standardizing communication through connector-driven MCP servers, it ensures consistent data exchange, governance, and trust across every agent interaction.
Agent Loop offers three ways to bring MCP tools into your workflows:
- Bring Your Own MCP connector – Point to any external MCP server using its URL and credentials, instantly surfacing its published tools in your agent. An example of this type of MCP Server is using Logic Apps as an MCP Server which enables you to dynamically build MCP Servers using Logic Apps connectors.
- Managed MCP connector – Access Azure-hosted MCP servers through the familiar managed connector experience, with shared connections and Azure-managed catalogs. Inside of Logic Apps, there are already a set of managed MCP servers that are ready to use. Popular MCP Servers include:
- Office 365 Email
- Office 365 Calendar
- Salesforce
- Microsoft Learn
- Atlassian Jira
- GitHub
- Custom MCP connector – Build and publish your own OpenAPI-based MCP connector to expose private or tenant-scoped MCP servers. Idea for reusability of MCPs across organization.
Managed and Custom MCP connectors support on-behalf-of (OBO) authentication, allowing agents to call MCP tools using the end user’s identity. This provides user-context-aware, permission-sensitive tool access across your intelligent workflows.
Demo
To view how you can setup using MCP Servers inside of Agent Loop, please review the following video.
Additional Resources
For additional resources:
Microsoft