Teams MCP - Operator Manual — Unique AI Documentation
Teams MCP - Operator Manual
Overview
This guide provides IT operators with the technical information needed to deploy, configure, and maintain the Teams MCP Server.
The Teams MCP Server exposes 12 MCP tools across two categories:
Chat / messaging tools —
list_teams,list_channels,list_chats,get_chat_messages,get_channel_messages,search_messages,send_chat_message,send_channel_messageTranscript / KB tools —
ingest_meeting,verify_kb_integration_status,start_kb_integration,stop_kb_integration
Chat tools let users read, search, and send messages in their Teams channels and chats. Transcript tools manage the Microsoft Graph subscription that ingests meeting transcripts into the Unique knowledge base, and allow users to manually trigger ingestion.
For end-user and administrator documentation, see the Teams MCP Overview. For a full tool reference, see Technical — Tools.
Documentation
| Document | Description |
|---|---|
| Deployment | Kubernetes deployment, Helm charts, infrastructure requirements |
| Configuration | Environment variables, feature flags, tuning |
| Authentication | Microsoft Entra ID app registration, OAuth setup |
| Local Development | Setting up a development environment |
| FAQ | 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
- incomplete PostgreSQL database provisioned
- incomplete RabbitMQ instance running
- incomplete Kubernetes namespace created
- incomplete Kong route configured for public access
Microsoft Entra ID
- incomplete App registration created ( Authentication Guide)
- incomplete API permissions granted
- incomplete Admin consent completed
- incomplete Client secret configured
Application
- incomplete Helm values configured ( Configuration Guide)
- incomplete Secrets created in Kubernetes
- incomplete Helm chart deployed ( Deployment Guide)
- incomplete Health checks passing
Verification
- incomplete OAuth flow works end-to-end
- incomplete Webhook endpoint accessible from Microsoft
- incomplete Test transcript captured successfully
- incomplete Chat tools operational: connect as a test user and confirm
list_teamsreturns the user's teams