MCP Teams Server

An MCP server that enables AI agents to interact with Microsoft Teams: reading channel messages, creating discussion threads, replying to threads, mentioning members, and retrieving channel member lists.

Evaluated Mar 06, 2026 (0d ago) vlatest
Homepage ↗ Repo ↗ Other microsoft-teams teams messaging enterprise python azure inditex
⚙ Agent Friendliness
67
/ 100
Can an agent use this?
🔒 Security
86
/ 100
Is it safe for agents?
⚡ Reliability
80
/ 100
Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality
65
Documentation
70
Error Messages
50
Auth Simplicity
65
Rate Limits
65

🔒 Security

TLS Enforcement
100
Auth Strength
85
Scope Granularity
82
Dep. Hygiene
82
Secret Handling
82

Microsoft Teams MCP. Azure AD app registration + OAuth2. Corporate messaging — potentially sensitive communications. Graph API scopes for Teams data. Minimal scopes for agent operations.

⚡ Reliability

Uptime/SLA
85
Version Stability
80
Breaking Changes
75
Error Recovery
78
AF Security Reliability

Best When

Your organization uses Microsoft Teams and you need an AI agent to post updates, monitor channel discussions, or interact with team members programmatically via MCP.

Avoid When

You need Slack integration, personal chat messaging, or your IT policy restricts Azure app registrations with Teams permissions.

Use Cases

  • • Automating Teams channel updates from an AI assistant (status reports, incident notifications)
  • • Reading and summarizing Teams thread conversations from an LLM client
  • • Mentioning specific team members in AI-generated channel messages

Not For

  • • Personal Teams chat (DMs); appears focused on channel operations only
  • • Teams calling or meetings integration
  • • Organizations without Azure Entra ID app registration capabilities

Interface

REST API
No
GraphQL
No
gRPC
No
MCP Server
Yes ↗
SDK
No
Webhooks
No

Authentication

Methods: client_credentials env_var
OAuth: Yes Scopes: Yes

Requires Azure Entra ID app registration with six environment variables: TEAMS_APP_ID, TEAMS_APP_PASSWORD, TEAMS_APP_TYPE, TEAMS_APP_TENANT_ID, TEAM_ID, TEAMS_CHANNEL_ID. Client credentials (app) flow.

Pricing

Model: open_source
Free tier: Yes
Requires CC: No

Apache-2.0 open source. Microsoft Teams / Azure usage is subject to your Microsoft 365 licensing.

Agent Metadata

Pagination
none
Idempotent
Partial
Retry Guidance
Not documented

Known Gotchas

  • ⚠ Setup requires an Azure Entra ID app registration with appropriate Graph API permissions; non-trivial for first-time Azure users.
  • ⚠ TEAMS_CHANNEL_ID must be URL-encoded; raw channel IDs from the Teams UI will not work.
  • ⚠ Single-tenant vs multi-tenant configuration (TEAMS_APP_TYPE) must match the Azure app registration exactly.
  • ⚠ No pagination documented for channel message history retrieval; large channels may be truncated.
  • ⚠ Creating duplicate threads on retry is a real risk since the server has no idempotency keys.

Alternatives

mcp-server-slack mcp-server-chatsum ms365-mcp

Full Evaluation Report

Detailed scoring breakdown, competitive positioning, security analysis, and improvement recommendations for MCP Teams Server.

$99
API endpoint ↗ Agent guide ↗ Report inaccuracy

Scores are editorial opinions as of 2026-03-06.

5178
Packages Evaluated
26151
Need Evaluation
173
Need Re-evaluation
♥
Community Powered