Skip to content

Commit 5857df2

Browse files
committed
Refine C# editions for clarity and accuracy
1 parent 2e81037 commit 5857df2

1 file changed

Lines changed: 20 additions & 20 deletions

File tree

articles/azure-functions/scenario-mcp-apps.md

Lines changed: 20 additions & 20 deletions
Original file line numberDiff line numberDiff line change
@@ -15,14 +15,7 @@ zone_pivot_groups: programming-languages-set-functions
1515

1616
In this quickstart, you create a Model Context Protocol (MCP) server from a template project by using the Azure Developer CLI (`azd`). This MCP server uses the Azure Functions MCP extension to create [MCP Apps](https://blog.modelcontextprotocol.io/posts/2026-01-26-mcp-apps/), which are tools that return rich, interactive user interfaces. You can also use the MCP server extension to [create text-based tools](./scenario-custom-remote-mcp-server.md).
1717

18-
<<<<<<< qs-update
19-
This quickstart uses the Azure Functions MCP extension to build an MCP App using the MCP tool and resource trigger. After running the project locally and verifying your code by using GitHub Copilot, you deploy it to a new serverless function app in Azure Functions that follows current best practices for secure and scalable deployments.
20-
21-
>[!TIP]
22-
>MCP tools built with the Azure Functions MCP extension don't have to return results in interactive UIs. If your server only needs text-based tools, see [Quickstart: Build a custom remote MCP server using Azure Functions](scenario-custom-remote-mcp-server.md).
23-
=======
2418
After running the project locally and verifying your code by using GitHub Copilot, you deploy it to a new serverless function app in Azure Functions that follows current best practices for secure and scalable deployments.
25-
>>>>>>> main
2619

2720
Because the new app runs on the Flex Consumption plan, which follows a _pay-for-what-you-use_ billing model, completing this quickstart incurs a small cost of a few USD cents or less in your Azure account.
2821

@@ -44,7 +37,7 @@ This article supports version 2 of the Python programming model for Azure Functi
4437
::: zone-end
4538
::: zone pivot="programming-language-csharp"
4639
+ [.NET 10 SDK](https://dotnet.microsoft.com/download)
47-
+ [Azure Developer CLI](https://learn.microsoft.com/azure/developer/azure-developer-cli/install-azd) **1.23.x or above**
40+
+ [Azure Developer CLI](https://learn.microsoft.com/azure/developer/azure-developer-cli/install-azd) version 1.23.x or a later version
4841
::: zone-end
4942
<!-- replace when supported
5043
::: zone pivot="programming-language-javascript,programming-language-typescript" -->
@@ -84,7 +77,7 @@ Use the Azure Developer CLI to create an Azure Functions code project from a tem
8477

8578
::: zone-end
8679
::: zone pivot="programming-language-csharp"
87-
2. Open a terminal in Visual Studio Core and run:
80+
2. Run the following command in the Terminal:
8881

8982
```console
9083
azd init --template remote-mcp-functions-dotnet -e mcpweather-dotnet
@@ -166,15 +159,13 @@ The MCP Apps weather tool includes a frontend application that you must build be
166159
cd ../..
167160
```
168161

169-
::: zone-end
162+
::: zone-end
170163
::: zone pivot="programming-language-csharp,programming-language-python,programming-language-typescript"
171164
## Run your MCP server locally
172-
::: zone-end
173-
165+
::: zone-end
174166
::: zone pivot="programming-language-csharp"
175-
When Visual Studio Code asks you to pick a default project because there are two apps in the .NET template, select **src/McpWeatherApp**.
176-
::: zone-end
177-
167+
When prompted, select **src/McpWeatherApp**. You see this prompt because there are two projects in the solution, and the other project isn't used by this article.
168+
::: zone-end
178169
::: zone pivot="programming-language-csharp,programming-language-python,programming-language-typescript"
179170
[!INCLUDE [run-locally](../../includes/functions-mcp-run-locally.md)]
180171

@@ -247,27 +238,36 @@ After verifying the MCP Apps tools locally, you can publish the project to Azure
247238

248239
## Deploy to Azure
249240
::: zone-end
250-
251-
::: zone pivot="programming-language-csharp,programming-language-python,programming-language-typescript"
241+
::: zone pivot="programming-language-python,programming-language-typescript"
252242
[!INCLUDE [deploy-azure](../../includes/functions-mcp-deploy-azure.md)]
253243
::: zone-end
254244

255245
::: zone pivot="programming-language-csharp"
256246
This project is configured to use `azd` to deploy this project to a new function app in a Flex Consumption plan in Azure. The project includes a set of Bicep files that `azd` uses to create a secure deployment to a Flex Consumption plan that follows best practices.
257247

258-
1. Set `DEPLOY_SERVICE` to provision `weather` app related resources:
248+
1. In the Terminal, run this `azd env set` command:
249+
259250
```console
260251
azd env set DEPLOY_SERVICE weather
261252
```
262253

263-
1. Provision the resources:
254+
This command sets the `DEPLOY_SERVICE` variable to provision `weather` app related resources
255+
256+
257+
1. Run the `azd provision` command and supply the required parameters to provision resources:
258+
264259
```console
265260
azd provision
266261
```
267262

263+
| Parameter | Description |
264+
| ---- | ---- |
265+
| _Azure subscription_ | Subscription in which your resources are created. |
266+
| _Azure location_ | Azure region in which to create the resource group that contains the new Azure resources. Only regions that currently support the Flex Consumption plan are shown. |
267+
| _vnetEnabled_ | `False` to skip creating virtual network resources, which simplifies the deployment. |
268268
When prompted, pick your subscription, an Azure region for the resources, and choose `false` to skip creating virtual network resources to simplify the deployment.
269269

270-
1. Deploy the `weather` app:
270+
1. Run the `azd deploy` command to deploy the `weather` app to Azure:
271271

272272
```console
273273
azd deploy --service weather

0 commit comments

Comments
 (0)