Remote MCP Servers using Azure Functions : Getting Started

Project Overview

This project implements a Model Context Protocol (MCP) server using Azure Functions with .NET 10. The application exposes multiple tools through MCP that can be invoked by MCP-compatible clients for various operations including health checks, product information retrieval, and user profile management.

Table of Contents

• Architecture
• Technology Stack
• Project Structure
• MCP Tools
• Getting Started
• Configuration
• Testing with VS Code
• Development
• Deployment
• Dependencies

Architecture

The application follows a serverless architecture pattern using Azure Functions with the isolated worker model. It leverages the Model Context Protocol to expose tools that can be consumed by AI assistants and other MCP clients.

Key Components:

• Azure Functions Runtime: v4
• Worker Model: Isolated (.NET 10)
• Protocol: Model Context Protocol (MCP)
• Monitoring: Application Insights integration
• Logging: Console logging with configurable log levels

Technology Stack

• .NET: 10.0
• Azure Functions: v4
• Model Context Protocol: v0.5.0-preview.1
• Application Insights: v2.23.0
• Runtime: dotnet-isolated worker

Project Structure

src/
 FunctionApp/
     Functions/
        PingFunction.cs
        ProductInfoFunction.cs
        UserProfileFunction.cs
     Program.cs
     FunctionApp.csproj
     host.json
     local.settings.json

Directory Layout

MCP Tools

The application exposes three MCP tools:

1. PingFunction

Purpose: Health check endpoint to verify the MCP server is running.

Trigger: McpToolTrigger

• Name: PingFunction
• Description: "Check if the MCP server is running."

Parameters:

• message (string, optional): Optional message to echo back

Response:

• Returns "? MCP server is alive." if no message provided
• Echoes back the message if provided: "? MCP server received: {message}"

Example Usage:

{
  "tool": "PingFunction",
  "parameters": {
    "message": "Hello"
  }
}

2. ProductInfoFunction

Purpose: Retrieve product information by product code.

Trigger: McpToolTrigger

• Name: ProductInfoFunction
• Description: "Get product information by product code."

Parameters:

• productCode (string, required): The product code

Supported Product Codes:

• P100: Laptop - $1200 - Available
• P200: Monitor - $300 - Out of stock
• P300: Keyboard - $80 - Available

Response: Returns formatted product information including:

• Product name
• Price
• Stock availability

Example Usage:

{
  "tool": "ProductInfoFunction",
  "parameters": {
    "productCode": "P100"
  }
}

Response:

Product: Laptop
Price: $1200
Stock: Available

3. UserProfileFunction

Purpose: Retrieve basic user profile information.

Trigger: McpToolTrigger

• Name: UserProfileFunction
• Description: "Get basic user profile information."

Parameters:

• userId (string, required): The user identifier

Supported User IDs:

• alice: Administrator - Active
• bob: Developer - Active
• charlie: Viewer - Disabled

Response: Returns formatted user profile including:

• Name
• Role
• Status

Example Usage:

{
  "tool": "UserProfileFunction",
  "parameters": {
    "userId": "alice

... [View full README on GitHub](https://github.com/azurecorner/remote-MCP-servers-using-azure-functions#readme)