Teams MCP - Technical Manual
1 min read
Overview
This section contains detailed technical documentation for developers and architects working with the Teams MCP Server.
Note: The Teams MCP Server is both an MCP server and a connector — it exposes 12 MCP tools (8 chat/messaging + 4 transcript/KB) that AI clients invoke on demand, and once a user connects their account, it automatically ingests meeting transcripts into the Unique knowledge base in the background. This contrasts with pure connector-style servers which ingest data silently without exposing tools.
Key distinction: meeting transcripts and recordings are ingested into Unique (copied into the knowledge base) and queried from that stored copy; Teams chat and channel messages are accessible in Unique through the MCP tools but are never ingested — they are fetched live from the Microsoft Graph API and exist only in Microsoft. "Not ingested" is about storage, not accessibility. See README — Where the Data Lives.
Documentation
Document | Description |
|---|---|
System components, infrastructure, and data model | |
Sequence diagrams for user connection, subscriptions, and processing | |
Microsoft Graph permissions with least-privilege justification | |
Encryption, authentication, and threat model | |
Transcript-ingestion webhook subscription lifecycle (create, renew, status, removal) | |
Full reference for all 12 MCP tools (8 chat/messaging + 4 transcript/KB) | |
Frequently asked questions |