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 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

  1. Infrastructure

    1. incomplete PostgreSQL database provisioned
    2. incomplete RabbitMQ instance running
    3. incomplete Kubernetes namespace created
    4. incomplete Kong route configured for public access
  2. Microsoft Entra ID

    1. incomplete App registration created ( Authentication Guide)
    2. incomplete API permissions granted
    3. incomplete Admin consent completed
    4. incomplete Client secret configured
  3. Application

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

    1. incomplete OAuth flow works end-to-end
    2. incomplete Webhook endpoint accessible from Microsoft
    3. incomplete Test transcript captured successfully
    4. incomplete Chat tools operational: connect as a test user and confirm list_teams returns the user's teams