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
* Add Entra auth proxy
* Reverting unneeded changes
* Fixes to env vars and readme
* Fix ManagedIdentityCredential in prod so it knows to use user-assigned
* Address PR feedback
* Move to a single variable for auth control
* Fix ruff error
* Revert mcp.json changes
* Fix ps1 auth init
* Tweaks while working on slides
* Updates to OTel and README
* Remove restore
* Readme fix
* Log level fix
* Remove keycloak from agentframework example
Copy file name to clipboardExpand all lines: README.md
+54-3Lines changed: 54 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -121,7 +121,7 @@ The `.vscode/launch.json` provides a debug configuration to attach to an MCP ser
121
121
3. Press `Cmd+Shift+D` to open Run and Debug
122
122
4. Select "Attach to MCP Server (stdio)" configuration
123
123
5. Press `F5` or the play button to start the debugger
124
-
6. Select the expenses-mcp-debug server in GitHub Copilot Chat tools
124
+
6. Select the "expenses-mcp-debug" server in GitHub Copilot Chat tools
125
125
7. Use GitHub Copilot Chat to trigger the MCP tools
126
126
8. Debugger pauses at breakpoints
127
127
@@ -191,7 +191,6 @@ You can use the [.NET Aspire Dashboard](https://learn.microsoft.com/dotnet/aspir
191
191
uv run servers/basic_mcp_http.py
192
192
```
193
193
194
-
195
194
4. View the dashboard at: http://localhost:18888
196
195
197
196
---
@@ -288,6 +287,58 @@ You can try the [Azure pricing calculator](https://azure.com/e/3987c81282c84410b
288
287
289
288
⚠️ To avoid unnecessary costs, remember to take down your app if it's no longer in use, either by deleting the resource group in the Portal or running `azd down`.
290
289
290
+
### Use deployed MCP server with GitHub Copilot
291
+
292
+
The URL of the deployed MCP server is available in the azd environment variable `MCP_SERVER_URL`, and is written to the `.env` file created after deployment.
293
+
294
+
1. To avoid conflicts, stop the MCP servers from `mcp.json` and disable the expense MCP servers in GitHub Copilot Chat tools.
295
+
2. Select "MCP: Add Server" from the VS Code Command Palette
296
+
3. Select "HTTP" as the server type
297
+
4. Enter the URL of the MCP server, based on the `MCP_SERVER_URL` environment variable.
298
+
5. Enable the MCP server in GitHub Copilot Chat tools and test it with an expense tracking query:
299
+
300
+
```text
301
+
Log expense for 75 dollars of office supplies on my visa last Friday
302
+
```
303
+
304
+
### Running the server locally
305
+
306
+
After deployment sets up the required Azure resources (Cosmos DB, Application Insights), you can also run the MCP server locally against those resources:
307
+
308
+
```bash
309
+
# Run the MCP server
310
+
cd servers && uvicorn deployed_mcp:app --host 0.0.0.0 --port 8000
311
+
```
312
+
313
+
### Viewing traces in Azure Application Insights
314
+
315
+
By default, OpenTelemetry tracing is enabled for the deployed MCP server, sending traces to Azure Application Insights.
316
+
317
+
1. Open the Azure Portal and navigate to the Application Insights resource created during deployment (named `<project-name>-appinsights`).
318
+
2. In Application Insights, go to "Transaction Search" to view traces from the MCP server
319
+
3. You can filter and analyze traces to monitor performance and diagnose issues.
320
+
321
+
### Viewing traces in Logfire
322
+
323
+
You can also view OpenTelemetry traces in [Logfire](https://logfire.io/) by configuring the MCP server to send traces there.
324
+
325
+
1. Create a Logfire account and get your write token from the Logfire dashboard.
326
+
327
+
2. Set the azd environment variables to enable Logfire:
328
+
329
+
```bash
330
+
azd env set OPENTELEMETRY_PLATFORM logfire
331
+
azd env set LOGFIRE_TOKEN <your-logfire-write-token>
332
+
```
333
+
334
+
3. Provision and deploy:
335
+
336
+
```bash
337
+
azd up
338
+
```
339
+
340
+
4. Open the Logfire dashboard to view traces from the MCP server.
341
+
291
342
---
292
343
293
344
## Deploy to Azure with private networking
@@ -461,7 +512,7 @@ The following environment variables are automatically set by the deployment hook
461
512
462
513
These are then written to `.env` by the postprovision hook for local development.
463
514
464
-
### Testing locally
515
+
### Testing the Entra OAuth server locally
465
516
466
517
After deployment, you can test locally with OAuth enabled:
0 commit comments