mcp -azure-function

This MCP server is built to work with Azure Functions using the MCP (Model Context Protocol) framework. It enables you to run a local MCP server powered by the Azure Functions runtime and connect it to Copilot Chat as an agent-like backend. You can test and inspect the MCP stream with the MCP inspector and then integrate it into GitHub Copilot Chat by configuring the proper mcp.json settings in VS Code. The setup described here uses the local Azure Functions host (func start) to serve the MCP endpoints that Copilot will interact with via Server-Sent Events (SSE).

To use it, first run the local Azure Functions host with the MCP extension enabled. Then verify the MCP server is exposing the expected SSE endpoint (for example, http://localhost:7071/runtime/webhooks/mcp/sse) using the MCP inspector. In Copilot Chat, provide the server definition (local-mcp) and, if needed, an Azure Function key and function name when you deploy to Azure. The repository's example configurations show how to reference a local SSE endpoint and how to wire remote Azure Functions behind an API key for access.

Prerequisites:

• .NET SDK (for example, .NET 6 or later) and Azure Functions Core Tools installed on your machine.
• Azure Functions Core Tools (func) available in your PATH.
• Node.js and npm if you plan to use the MCP inspector and related tooling from npm.

Installation steps:

1. Install the NuGet package in your Azure Functions project to enable MCP support: dotnet add package Microsoft.Azure.Functions.Worker.Extensions.Mcp --version 1.0.0-preview.2

2. Initialize and run your Azure Functions project locally: func start

3. Test the MCP endpoint with the inspector to ensure the SSE stream is exposed: npx @modelcontextprotocol/inspector http://localhost:7071/runtime/webhooks/mcp/sse

4. If configuring Copilot Chat, create the VS Code mcp.json (or add to .vscode/settings.json) with the local SSE URL as shown in the example configuration provided in the repository. Example: { "inputs": [ { "type": "promptString", "id": "mcp-azure-function-key", "description": "Azure Function Key to access the MCP server on Azure", "password": true }, { "type": "promptString", "id": "mcp-azure-function-name", "description": "Azure Function name to access the MCP server on Azure" } ], "servers": { "local-mcp-azure-function": { "type": "sse", "url": "http://localhost:7071/runtime/webhooks/mcp/sse" } } }

5. If you want to deploy to Azure, follow your usual Azure Functions deployment flow (Azure CLI, CI/CD, or VS Code) and ensure the function key is accessible if you expose the endpoint publicly.

Tips and considerations:

• The MCP server is run via the Azure Functions host locally. Ensure your environment variables are set correctly for local testing and for any Azure deployment you plan to use.
• When using Copilot Chat, you may need to add a local or remote mcp entry with either a local URL or a protected remote URL. The repository examples show how to configure both local and remote endpoints.
• If you encounter connection issues, confirm that the Functions host is running, the SSE endpoint is reachable, and any firewall rules allow access to the port (default 7071 for local host).
• For Azure deployments, keep track of the function key and the function name. Update the Copilot configuration to reference the remote endpoint and include authentication headers if required by your deployment.
• The NuGet package is the recommended integration point for MCP support in the Azure Functions runtime; ensure you are using a compatible .NET isolated worker model as described in the package documentation.