improving the devex for mcp clients

Author: paulyuk

README.md

@@ -62,7 +62,7 @@ An Azure Storage Emulator is needed for this particular sample because we will s
 
 Note by default this will use the webhooks route: `/runtime/webhooks/mcp/sse`.  Later we will use this in Azure to set the key on client/host calls: `/runtime/webhooks/mcp/sse?code=<system_key>`
 
-## Use the MCP server from within a client/host
+## Connect to the *local* MCP server from within a client/host
 
 ### VS Code - Copilot Edits
 
@@ -120,13 +120,18 @@ azd env set VNET_ENABLED true
 
 Additionally, [API Management]() can be used for improved security and policies over your MCP Server, and [App Service built-in authentication](https://learn.microsoft.com/en-us/azure/app-service/overview-authentication-authorization) can be used to set up your favorite OAuth provider including Entra.  
 
-### Connect to your function app from a client
+## Connect to your *remote() MCP server function app from a client
 
 Your client will need a key in order to invoke the new hosted SSE endpoint, which will be of the form `https://<funcappname>.azurewebsites.net/runtime/webhooks/mcp/sse`. The hosted function requires a system key by default which can be obtained from the [portal](https://learn.microsoft.com/en-us/azure/azure-functions/function-keys-how-to?tabs=azure-portal) or the CLI (`az functionapp keys list --resource-group <resource_group> --name <function_app_name>`). Obtain the system key named `mcp_extension`.
 
-For MCP Inspector, you can include the key in the URL: `https://<funcappname>.azurewebsites.net/runtime/webhooks/mcp/sse?code=<your-mcp-extension-system-key>`.
+### Connect to remote MCP server in MCP Inspector
+For MCP Inspector, you can include the key in the URL: 
+```plaintext
+https://<funcappname>.azurewebsites.net/runtime/webhooks/mcp/sse?code=<your-mcp-extension-system-key>
+```
 
-For GitHub Copilot within VS Code, you should instead set the key as the `x-functions-key` header in `mcp.json`, and you would just use `https://<funcappname>.azurewebsites.net/runtime/webhooks/mcp/sse` for the URL. The following example uses an input and will prompt you to provide the key when you start the server from VS Code:
+### Connect to remote MCP server in VS Code - GitHub Copilot
+For GitHub Copilot within VS Code, you should instead set the key as the `x-functions-key` header in `mcp.json`, and you would just use `https://<funcappname>.azurewebsites.net/runtime/webhooks/mcp/sse` for the URL. The following example uses an input and will prompt you to provide the key when you start the server from VS Code.  Note [mcp.json]() has already been included in this repo and will be picked up by VS Code.  Click Start on the server to be prompted for values including `functionapp-name` (in your /.azure/*/.env file) and `functions-mcp-extension-system-key` which can be obtained from CLI command above or API Keys in the portal for the Function App.  
 
 ```json
 {
@@ -136,20 +141,31 @@ For GitHub Copilot within VS Code, you should instead set the key as the `x-func
             "id": "functions-mcp-extension-system-key",
             "description": "Azure Functions MCP Extension System Key",
             "password": true
+        },
+        {
+            "type": "promptString",
+            "id": "functionapp-name",
+            "description": "Azure Functions App Name"
         }
     ],
     "servers": {
-        "my-mcp-server": {
+        "remote-mcp-function": {
             "type": "sse",
-            "url": "<funcappname>.azurewebsites.net/runtime/webhooks/mcp/sse",
+            "url": "https://${input:functionapp-name}.azurewebsites.net/runtime/webhooks/mcp/sse",
             "headers": {
                 "x-functions-key": "${input:functions-mcp-extension-system-key}"
             }
+        },
+        "local-mcp-function": {
+            "type": "sse",
+            "url": "http://0.0.0.0:7071/runtime/webhooks/mcp/sse"
         }
     }
 }
 ```
 
+Click Start on the server to be prompted for values including `functionapp-name` (in your /.azure/*/.env file) and `functions-mcp-extension-system-key` which can be obtained from CLI command above or API Keys in the portal for the Function App.
+
 ## Redeploy your code
 
 You can run the `azd up` command as many times as you need to both provision your Azure resources and deploy code updates to your function app.
@@ -168,7 +184,7 @@ azd down
 
 ## Source Code
 
-The function code for the `GetSnippet` and `SaveSnippet` endpoints are defined in [`SnippetsTool.cs`](./dotnet/). The `McpToolsTrigger` attribute applied to the async `Run` method exposes the code function as an MCP Server.
+The function code for the `GetSnippet` and `SaveSnippet` endpoints are defined in [`SnippetsTool.cs`](./src/SnippetsTool.cs). The `McpToolsTrigger` attribute applied to the async `Run` method exposes the code function as an MCP Server.
 
 This shows the code for a few MCP server examples (get string, get object, save object):