Teams MCP - Operator Manual
1 min read
Overview
This guide provides IT operators with the technical information needed to deploy, configure, and maintain the Teams MCP Server.
Note: The Teams MCP Server is a connector-style MCP server, not a traditional MCP server. It does not provide tools, prompts, resources, or other MCP capabilities. Once users connect, it automatically ingests meeting transcripts into the Unique knowledge base without requiring any additional interaction.
For end-user and administrator documentation, see the Teams MCP Overview.
Documentation
Document | Description |
|---|---|
Kubernetes deployment, Helm charts, infrastructure requirements | |
Environment variables, feature flags, tuning | |
Microsoft Entra ID app registration, OAuth setup | |
Setting up a development environment | |
Frequently asked questions and common mistakes |
Architecture Overview
The Teams MCP Server runs as a single pod that handles both API requests and background processing via RabbitMQ consumers.
Quick Start
Unique SaaS
After granting admin consent, no additional technical information is required from you. Unique configures the entire deployment using your existing tenant context.
Unique will provide you with the MCP server endpoint URL once the deployment is ready.
Infrastructure Requirements
Component | Requirement | Notes |
|---|---|---|
Kubernetes | 1.25+ | Any Kubernetes distribution |
PostgreSQL | 14+ | Managed service recommended |
RabbitMQ | 3.12+ | With management plugin |
Kong Gateway | 3.x | Handles ingress and TLS termination |
DNS | Public hostname | For Microsoft webhook callbacks |
Deployment Checklist
Infrastructure
Microsoft Entra ID
Application
Verification