Teams MCP - Operator Manual

2 min read

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 8 MCP tools — list_teams, list_channels, list_chats, get_chat_messages, get_channel_messages, search_messages, send_chat_message, send_channel_message — that let users read, search, and send messages in their Teams chats and channels. Every call is served live from Microsoft Graph; nothing is stored in Unique.

Meeting transcript capture is a separate, opt-in capability

Setting UNIQUE_INTEGRATION=enabled additionally captures meeting transcripts and recordings into the Unique knowledge base, which requires RabbitMQ, admin consent for the meeting scopes, a Zitadel service account, and a knowledge-base root scope. Enable it only if that is what you want — see the Recordings & Transcripts Operator Manual. Everything on this page applies to both modes.

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. With transcript capture enabled it additionally receives webhooks from Microsoft Graph, consumes them from RabbitMQ, and calls the Unique API — see the Recordings & Transcripts Operator Manual.

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
Kong Gateway	3.x	Handles ingress and TLS termination
DNS	Public hostname	For the MCP endpoint, and for Microsoft webhook callbacks when transcript capture is enabled
RabbitMQ	3.12+	Only with transcript capture enabled; with management plugin

Deployment Checklist

Infrastructure

1incomplete PostgreSQL database provisioned2incomplete Kubernetes namespace created3incomplete Kong route configured for public access

Microsoft Entra ID

1incomplete App registration created (Authentication Guide)2incomplete API permissions granted3incomplete Admin consent completed4incomplete Client secret configured

Application

1incomplete Helm values configured (Configuration Guide)2incomplete Secrets created in Kubernetes3incomplete Helm chart deployed (Deployment Guide)4incomplete Health checks passing

Verification

1incomplete OAuth flow works end-to-end2incomplete Chat tools operational: connect as a test user and confirm list_teams returns the user's teams

Deployments with transcript capture enabled have their own prerequisites and verification steps — see the Recordings & Transcripts enablement checklist.