You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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).
17
17
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
-
=======
24
18
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
26
19
27
20
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.
28
21
@@ -44,7 +37,7 @@ This article supports version 2 of the Python programming model for Azure Functi
@@ -166,15 +159,13 @@ The MCP Apps weather tool includes a frontend application that you must build be
166
159
cd ../..
167
160
```
168
161
169
-
::: zone-end
162
+
::: zone-end
170
163
::: zone pivot="programming-language-csharp,programming-language-python,programming-language-typescript"
171
164
## Run your MCP server locally
172
-
::: zone-end
173
-
165
+
::: zone-end
174
166
::: 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
178
169
::: zone pivot="programming-language-csharp,programming-language-python,programming-language-typescript"
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.
257
247
258
-
1. Set `DEPLOY_SERVICE` to provision `weather` app related resources:
248
+
1. In the Terminal, run this `azd env set` command:
249
+
259
250
```console
260
251
azd env set DEPLOY_SERVICE weather
261
252
```
262
253
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
+
264
259
```console
265
260
azd provision
266
261
```
267
262
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. |
268
268
When prompted, pick your subscription, an Azure region for the resources, and choose `false` to skip creating virtual network resources to simplify the deployment.
269
269
270
-
1. Deploy the `weather` app:
270
+
1. Run the `azd deploy` command to deploy the `weather` app to Azure:
0 commit comments