How microsoft/copilot-studio-mcp works
Project type and purpose
• This is a samples repository (“Microsoft Copilot Studio & Model Context Protocol (MCP) Samples”) demonstrating how to build small HTTP- or SSE-based services that integrate with Microsoft Copilot Studio via the MCP protocol.
• Each sample (in TypeScript or C#) shows a standalone microservice exposing either a streaming (SSE) endpoint or an HTTP endpoint, implementing simple domain logic (e.g., calculator, employee vacations, joke service) and calling the Copilot Studio API.
File structure
• Top-level:
– Solution file (.sln) for the C# sample.
– samples/ directory grouping independent subfolders by scenario and language.
• In each sample folder:
– Dockerfile and/or Azure infra definitions (jokesmcp-http-typescript/infra/*.bicep) for containerization and deployment.
– package.json, tsconfig.json for TypeScript projects; .csproj, appsettings.json for C#.
– src/: request handler (index.ts or server.ts / Program.cs), domain services under src/services or Services/, domain entities under Entities/.
• This consistent pattern signals a layered architecture in each sample: Presentation (HTTP/SSE), Application (Controller/Router), Domain (Services + Entities), External Integration (MCP client connector).
README for additional insights
• The README confirms this is not a monolithic app but a collection of usage samples for the MCP interface.
Final recommendations
• Be detailed: capture every layer from network boundary to domain logic to external API.
• Avoid overcrowding: collapse repeated patterns under a “common architecture” container and annotate specifics for each scenario.