AM

atea/mcp-server-concept

Developer tools

이 페이지는 AI로 자동 번역되었습니다. 기술적인 세부 사항은 원문을 확인하세요. 원문 보기

4 stars 9 forks 품질 59 트렌드 20

Start building your own MCP Servers. At the core of our approach is the Model Context Protocol. Develop MCP Servers that bridge the gap between Copilot agents and the systems, data, and workflows...

개요

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. 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 with authentication, telemetry, and token exchange already wired up - for scaffolding new MCP servers (C# project, Dockerfile, Bicep, CI/CD workflow, Copilot custom connector) - that guide you through deployment setup and server creation step by step - for building Docker images and deploying to Azure Container Apps Each MCP server runs as a containerised .NET 9 application on Azure Container Apps.

README

원문 README의 일부입니다. 원문 보기.

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 (three resource groups):

  • rg-{AcrName} — Azure Container Registry, shared by dev and prod
  • rg-{DevEnv} — dev environment: Container Apps Environment, Key Vault, Log Analytics, Application Insights, Storage Account, User-Assigned Managed Identity
  • rg-{ProdEnv} — prod environment: same resources as dev, fully isolated

Per server:

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

Prerequisites

Tool Purpose Install
.NET 9 SDK Build and run C# projects locally winget install Microsoft.DotNet.SDK.9
Azure CLI Provision Azure resources and manage roles winget install Microsoft.AzureCLI
GitHub CLI Configure Actions secrets and variables winget install GitHub.cli
GitHub에서 전체 README 보기

설치

This server does not publish a one-line install command.

Open the repository installation guide MCP 초보자라면? mcpskill.org 가이드부터 시작하세요 →