Microsoft has launched a public preview that permits Azure Logic Apps (Customary) to run as Mannequin Context Protocol (MCP) servers, exposing Logic Apps workflows as agent instruments discoverable and callable by MCP-capable purchasers (e.g., VS Code + Copilot).
What’s really transport
- Distant MCP server on Logic Apps (Customary): You configure a Customary logic app to host an MCP endpoint (
/api/mcp) and floor HTTP Request/Response workflows as instruments. Authentication is front-doored by Straightforward Auth; MCP endpoints default to OAuth 2.0. VS Code (≥1.102) contains GA MCP consumer assist for testing. - API Heart registration path (preview): You can even create/register MCP servers in Azure API Heart, the place chosen managed connector actions turn out to be instruments with cataloging and governance.
Key necessities and transport particulars
- Workflow form: Instruments should be carried out as HTTP Request set off (“When a HTTP request is acquired”) plus a Response motion.
- Auth & entry management: By default, MCP makes use of OAuth 2.0; Straightforward Auth enforces consumer/identification/tenant restrictions. Throughout setup, App Service authentication should permit unauthenticated requests (the MCP move nonetheless performs OAuth).
- Transports: Streamable HTTP works out of the field. SSE moreover requires VNET integration and
host.jsonsettingRuntime.Backend.EdgeWorkflowRuntimeTriggerListener.AllowCrossWorkerCommunication=true. - Enablement swap: MCP APIs are enabled by including
extensions.workflow.McpServerEndpoints.allow=truein host.json.
API Heart path: preview limitations that matter
When creating MCP servers by way of API Heart backed by Logic Apps, the present preview imposes the next limits:
- Begin with an empty Customary logic app useful resource.
- One connector per MCP server.
- Constructed-in service-provider and customized connectors aren’t supported on this path (managed connectors solely).
- One motion per instrument.
These constraints materially have an effect on instrument granularity and server format in bigger estates.
Why Customary (single-tenant) is the goal?
Customary runs on the single-tenant Logic Apps runtime (on Azure Features), helps a number of workflows per app, and integrates straight with digital networks and non-public endpoints—all related for exposing non-public methods safely to brokers and for predictable throughput/latency. In contrast, Consumption is multitenant, single-workflow per app, and pay-per-execution.
Tooling semantics and discoverability
Microsoft recommends including set off descriptions, parameter schemas/descriptions, and required markers to enhance agent instrument choice and invocation reliability. These annotations are learn by MCP purchasers and affect calling habits.
Connectors and enterprise attain
Organizations can entrance present workflows and a big catalog of Logic Apps connectors (cloud and on-prem) by MCP, turning them into callable agent instruments; Microsoft explicitly cites “greater than 1,400 connectors.”
Operations, governance, and testing
Run historical past plus Utility Insights/Log Analytics can be found for diagnostics and auditability. VS Code offers fast consumer validation by way of MCP: Add Server, together with OAuth sign-in and gear enumeration. Registering by way of API Heart brings discovery/governance to MCP servers throughout groups.
Manufacturing notes (preview)
- SSE requires each VNET and the cross-worker setting; with out these, use streamable HTTP.
- Straightforward Auth should be configured exactly (together with the “permit unauthenticated” toggle) or consumer sign-in flows will fail regardless of OAuth expectations.
- Throttling, idempotency, and schema versioning stay your accountability when wrapping connectors as instruments (not new, however now within the agent path). InfoQ highlights related operational considerations from early adopters.
Abstract
The preview cleanly MCP-enables Logic Apps (Customary): you expose HTTP-based workflows as OAuth-protected instruments; you may catalog them in API Heart; and you’ll attain non-public methods by single-tenant networking. For groups already invested in Logic Apps, this can be a low-friction, standards-aligned path to operationalize enterprise agent tooling—simply thoughts the API Heart limits, SSE stipulations, and Straightforward Auth nuances throughout rollout.
Try extra particulars right here. Be at liberty to take a look at our GitHub Web page for Tutorials, Codes and Notebooks. Additionally, be at liberty to observe us on Twitter and don’t overlook to hitch our 100k+ ML SubReddit and Subscribe to our E-newsletter.
For content material partnership with marktechpost.com, please TALK to us
Michal Sutter is an information science skilled with a Grasp of Science in Knowledge Science from the College of Padova. With a strong basis in statistical evaluation, machine studying, and knowledge engineering, Michal excels at reworking complicated datasets into actionable insights.
