Azure Functions Notes MCP Server

An Azure Functions-based MCP (Model Context Protocol) server implementation for managing notes and related functionality. This project demonstrates how to build a MCP server using Azure Functions, following best practices in a cloud native way.

Features

• MCP Protocol Support: Implements the Model Context Protocol for seamless integration with GitHub Copilot Chat and other MCP-aware clients
• Azure Functions: Built on .NET 8.0 using the latest Azure Functions runtime
• Infrastructure as Code: Complete infrastructure definition using Bicep templates
• Azure Integration: Integration with Azure services including Application Insights for monitoring
• Role-Based Access Control (RBAC): Access control for various Azure resources

MCP Tools

The server provides the following MCP tools for note management:

Tool Properties

• save_note:

  • title (required): The title or identifier for the note
  • category: The category of the note (e.g., meeting, task, idea, code-snippet, reminder)
  • tags: Comma-separated tags for organizing the note
  • content (required): The main content of the note

• get_note:

  • title (required): The title of the note to retrieve

• search_notes:

  • query: Search query for tags or category

• delete_note:

  • title (required): The title of the note to delete

Prerequisites

For local development:

• Azure Developer CLI (azd)
• .NET 8.0 SDK
• Azure Functions Core Tools
• An Azure subscription
• Visual Studio Code (recommended) with:
  • C# Dev Kit extension
  • Azure Functions extension
  • Bicep extension

Getting Started

Local Development

1. Clone the repository:

git clone <repository-url>
cd azure-functions-mcp-server

2. Install dependencies:

dotnet restore

3. Configure local settings:

• Copy local.settings.sample.json to local.settings.json

4. Run the project locally:

cd NotesMcp
func start

Using with VS Code and GitHub Copilot

To use the MCP tools in VS Code, you'll need to configure the MCP endpoint in your workspace. Create a .vscode/mcp.json file with the configuration based on your environment:

Local Development

When running the Function App locally:

{
    "servers": {
        "notes-mcp": {
            "type": "http",
            "url": "http://localhost:7071/runtime/webhooks/mcp"
        }
    }
}

Deployment

The project uses Azure Developer CLI (azd)

Deploy to Azure

1. Initialize the environment:

azd init

2. Login to Azure:

azd auth login

3. Provision and deploy:

azd up

This command will:

• Create required Azure resources
• Deploy the application code
• Set up configurations
• Output the Function App URL

To remove all resources:

azd down --purge

Usage after deployment

When using the deployed Function App in Azure the mcp.json from the client looks like this:

{
    "inputs": [
        {
            "type": "promptString",
            "id": "function-key",
            "description": "Azure Function App Key",
            "password": true
        }
    ],
    "servers": {
        "notes-mcp":

... [View full README on GitHub](https://github.com/arashjalalat/azure-functions-notes-mcp-server#readme)