Creativity · MCP — server

MCP Microsoft Teams Server

Microsoft Teams is the collaboration hub for much of the enterprise. The MCP Microsoft Teams Server uses Microsoft Graph to surface channels, messages, meetings, and chats to MCP clients — letting Claude read recent discussions, summarize threads, and post updates from a chat interface.

MCP facts

Kind: server
Ecosystem: anthropic-mcp
Language: TypeScript / Node.js
Transports: stdio

Capabilities

Tools: list_teams, list_channels, list_messages, send_message, list_chats, schedule_meeting
OAuth2 via Microsoft Identity Platform
Honors Graph API throttling

Install

npx -y @modelcontextprotocol-community/server-teams

Configuration

{
  "mcpServers": {
    "teams": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol-community/server-teams"],
      "env": {
        "TEAMS_TENANT_ID": "<tenant-id>",
        "TEAMS_CLIENT_ID": "<client-id>",
        "TEAMS_CLIENT_SECRET": "<client-secret>"
      }
    }
  }
}

Frequently asked questions

What permissions does it need?

Minimally Chat.Read, ChannelMessage.Read.All, and Team.ReadBasic.All. For posting, ChatMessage.Send and ChannelMessage.Send.All. Use delegated permissions where possible.

Can it read private chats?

Only with the signed-in user's consent; application permissions for chats are restricted and require admin policy changes.

Does it handle Teams meetings?

Yes — schedule_meeting creates a Teams-linked Outlook event; transcript access requires the OnlineMeetingTranscript.Read.All permission.

Sources

Microsoft Graph Teams API — accessed 2026-04-20
Model Context Protocol — accessed 2026-04-20