Atea MCP Concept

A scaffold repository for teams building their first Model Context Protocol (MCP) servers on Azure. Clone this repo, follow the setup steps, and have a production-ready MCP server deployed in your own Azure environment.

What Is This?

MCP servers expose tools that AI assistants (such as GitHub Copilot or Microsoft 365 Copilot) can invoke on behalf of users. This repository provides:

• A shared .NET class library with authentication, telemetry, and token exchange already wired up
• File templates for scaffolding new MCP servers (C# project, Dockerfile, Bicep, CI/CD workflow, Copilot custom connector)
• Copilot agent prompts that guide you through deployment setup and server creation step by step
• Reusable GitHub Actions workflows for building Docker images and deploying to Azure Container Apps

Architecture

Each MCP server runs as a containerised .NET 9 application on Azure Container Apps.

CI/CD and infrastructure:

GitHub Actions
    ├── Build Docker image → push to Azure Container Registry
    └── Deploy Bicep → Azure Container App
                            ├── reads secrets from Azure Key Vault
                            ├── reports telemetry to Application Insights
                            └── uses Managed Identity for Azure access

Runtime (inbound and outbound auth):

GitHub Copilot / Copilot Studio
        │  OAuth 2.0 (Entra ID)
        │  Bearer token in Authorization header
        ▼
┌───────────────────────────────────────────────┐
│  Azure Container App  (one per MCP server)    │
│  .NET 9 / ModelContextProtocol.AspNetCore     │
│  JWT Bearer + MCP WWW-Authenticate discovery  │
│  Tool  →  Service                             │
└───────────────────────────────────────────────┘
        │
        │  API Key  ──or──  OBO bearer token  ──or──  (no auth)
        ▼
   Upstream API  (Dynamics 365, Power BI, custom …)

Shared infrastructure (one per environment):

• Azure Container Registry — stores Docker images
• Container Apps Environment — hosts all MCP server containers
• Azure Key Vault — stores per-server secrets
• Log Analytics Workspace + Application Insights — observability
• Azure Storage Account — optional export target for large tool responses
• User-Assigned Managed Identity — grants containers access to Key Vault

Per server:

• Container App
• GitHub Actions workflow
• Bicep parameter file
• Copilot Custom Connector (swagger.json)

Prerequisites

Step-by-Step Guide

1. Fork the repository

Fork this repository into your own GitHub organisation using the Fork button at the top of the page, then clone your fork locally:

git clone https://github.com/{your-org}/{your-repo}.git
cd {your-repo}

2. Run /setup-deployment in GitHub Copilot Chat

Open GitHub Copilot Chat in VS Code and run:

/setup-deployment

This guided prompt will:

• Collect your environment name, location, and subscription ID
• Deploy all shared Azure infrastructure (Infrastructure/main.bicep)
• Create a service principal and store

... View full README on GitHub