-
Notifications
You must be signed in to change notification settings - Fork 21.9k
[Logic Apps] Update doc to include multiple MCP servers #127851
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
[Logic Apps] Update doc to include multiple MCP servers #127851
Conversation
|
@anandgmenon : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
|
@anandgmenon : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
|
Learn Build status updates of commit dc8a040:
|
| File | Status | Preview URL | Details |
|---|---|---|---|
| articles/logic-apps/set-up-model-context-protocol-server-standard.md | Details |
articles/logic-apps/set-up-model-context-protocol-server-standard.md
- Line 455, Column 1: [Warning: code-block-unclosed - See documentation]
Unclosed code block. Code blocks must begin and end with triple backticks (```).
For more details, please refer to the build report.
Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
|
Learn Build status updates of commit 5c5c49a:
|
| File | Status | Preview URL | Details |
|---|---|---|---|
| articles/logic-apps/set-up-model-context-protocol-server-standard.md | Details |
articles/logic-apps/set-up-model-context-protocol-server-standard.md
- Line 453, Column 1: [Warning: code-block-unclosed - See documentation]
Unclosed code block. Code blocks must begin and end with triple backticks (```).
For more details, please refer to the build report.
Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR updates the Logic Apps documentation to support configuring multiple MCP (Model Context Protocol) servers within a single Standard Logic App. Previously, the documentation covered setting up a single MCP server; now it describes how to organize workflows into multiple logical MCP servers, each with its own endpoint and set of tools.
Key Changes:
- Introduced mcpservers.json configuration file for defining multiple MCP servers
- Updated API endpoint structure from
/api/mcpto/api/mcpservers/{name}/mcp - Changed management API from
listMcpServerUrltolistMcpServersto retrieve all server endpoints
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| You can now configure multiple MCP servers within a single Standard Logic App. | ||
| This new approach provides a more scalable, organized, and flexible way to expose workflows as tools to large language models (LLMs), AI agents, and MCP clients. Each MCP server acts as an independent grouping of workflows that can be discovered and called separately from your MCP client. |
Copilot
AI
Nov 6, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Remove trailing double spaces at the end of lines 26 and 27. These are unnecessary and may cause formatting issues in Markdown renderers.
| 1. Next to the **host.json** file, select the edit icon (pencil). | ||
|
|
||
| 1. If a **mcpservers.json** file doesn’t already exist, create a new one: | ||
| - Select the `New File` icon, and name it `mcpservers.json`. |
Copilot
AI
Nov 6, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[nitpick] Use consistent formatting for UI elements. The term 'New File' should either be wrapped in backticks like New File or use bold formatting like New File to match the style used elsewhere in the document (e.g., line 293 uses Debug console).
| - Select the `New File` icon, and name it `mcpservers.json`. | |
| - Select the **New File** icon, and name it `mcpservers.json`. |
|
Can you review the proposed changes? Important: When the changes are ready for publication, adding a #label:"aq-pr-triaged" |
| Typically, large language models (LLMs) work with AI agents that handle and fulfill requests by using prebuilt *tools* that agents call to complete tasks, like send an email, query a database, or trigger a workflow. In Azure Logic Apps, you can jumpstart building these tools by reconfiguring a Standard logic app as your own *remote* Model Context Protocol (MCP) server. This capability means that you can expose existing workflows as tools that LLMs, AI agents, and MCP clients can use to interact with enterprise resources and assets. In this context, *remote* means that the MCP server runs outside the environment where the interface for your AI agent interface. | ||
|
|
||
| You can now configure multiple MCP servers within a single Standard Logic App. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This info appears too early in the introduction because the reader is just learning about MCP servers and disrupts the reading flow with "feature" info. Also, related sentences should appear on the same numbered "line", not separate lines.
You changed the "single MCP" scenario to a "multi-MCP" scenario. What if the customer just wants one MCP? Do they follow the same directions but define only one MCP server? Or, do they follow different directions for a single MCP server? If the steps are different, you need to have both sets of steps.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
no the steps are the same, we now suggest using this approach rather than the older one
| Typically, large language models (LLMs) work with AI agents that handle and fulfill requests by using prebuilt *tools* that agents call to complete tasks, like send an email, query a database, or trigger a workflow. In Azure Logic Apps, you can jumpstart building these tools by reconfiguring a Standard logic app as your own *remote* Model Context Protocol (MCP) server. This capability means that you can expose existing workflows as tools that LLMs, AI agents, and MCP clients can use to interact with enterprise resources and assets. In this context, *remote* means that the MCP server runs outside the environment where the interface for your AI agent interface. | ||
|
|
||
| You can now configure multiple MCP servers within a single Standard Logic App. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We never capitalize "logic app".
| You can now configure multiple MCP servers within a single Standard Logic App. | |
| You can now configure multiple MCP servers within a single Standard logic app resource. |
ecfan
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You'll need to recreate this PR in our internal repo.
No description provided.