Microsoft Teams
Connect Claude to Microsoft Teams — read/send messages, list channels, search chats.
What can you do with Microsoft Teams?
- One-click connect — visit
/connect, sign in with Microsoft, done - Multi-tenant — any Microsoft 365 organization, any user
- 11 tools — teams, channels, messages, chats, search, profile
- Dual transport — STDIO for Claude Code, HTTP/SSE for Cowork & remote
- Multi-user — each session gets isolated OAuth tokens
- Auto-detect — picks the right transport based on launch method
- Token caching — silent refresh, no re-login every session
- Retry logic — automatic retries on throttled Graph API calls
Install
Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).
microsoft-teams-mcp-serverclaude mcp add microsoft-teams -- npx -y microsoft-teams-mcp-server@1.0.2
{
"mcpServers": {
"microsoft-teams": {
"command": "npx",
"args": [
"-y",
"microsoft-teams-mcp-server@1.0.2"
]
}
}
}
Documentation
From the project's README on GitHub, refreshed weekly. Links open on GitHub.
Contents
Teams MCP Server
The first open-source Microsoft Teams connector for Claude. Any Microsoft 365 user can connect — just sign in with your work account. No setup, no credentials, no self-hosting required.
Read messages, list channels, search across Teams, send messages — all from Claude Code, Claude Desktop, or Claude Cowork.
Built by SurgeEnterpriseAI.
How It Works
┌─────────────┐ Click "Connect" ┌──────────────────────┐
│ Claude User │ ──────────────────────► │ Teams MCP Server │
│ (Cowork/ │ │ (hosted by Surge) │
│ Desktop/ │ SSE/MCP Protocol │ │
│ Code) │ ◄─────────────────────► │ ┌────────────────┐ │
└─────────────┘ │ │ OAuth (common) │ │
│ │ Any M365 user │ │
User signs in with their │ │ can sign in │ │
own Microsoft account │ └───────┬────────┘ │
─────────────────────► │ │ │
│ ┌───────▼────────┐ │
│ │ Microsoft │ │
│ │ Graph API │ │
│ └────────────────┘ │
└──────────────────────┘
The user connects their own Microsoft 365 account. They see their own teams, their own channels, their own messages. Each user's tokens are isolated. The server is the bridge — it never stores messages, just passes them through.
Features
- One-click connect — visit
/connect, sign in with Microsoft, done - Multi-tenant — any Microsoft 365 organization, any user
- 11 tools — teams, channels, messages, chats, search, profile
- Dual transport — STDIO for Claude Code, HTTP/SSE for Cowork & remote
- Multi-user — each session gets isolated OAuth tokens
- Auto-detect — picks the right transport based on launch method
- Token caching — silent refresh, no re-login every session
- Retry logic — automatic retries on throttled Graph API calls
- TypeScript — fully typed, clean architecture, MIT licensed
For Users: Connect in 1 Click
If someone is already hosting this server (e.g., on https://teams-mcp.surgeai.com):
- Claude asks you to connect Microsoft Teams
- You click the auth link
- Sign in with your Microsoft work account
- Done — Claude can now read your Teams
No API keys, no Azure portal, no setup.
For Developers: Self-Host
1. Clone & Install
git clone https://github.com/SurgeEnterpriseAI/teams-mcp-server.git
cd teams-mcp-server
npm install
npm run build
2. Azure AD App Registration
- Go to Azure Portal → App registrations → New registration
- Name:
Teams MCP Server - Supported account types: "Accounts in any organizational directory (Any Azure AD directory - Multitenant)"
- Redirect URI: Web →
https://your-server.com/auth/callback - Click Register
Configure:
- Certificates & secrets → New client secret → copy the Value
- API Permissions → Add Delegated (Microsoft Graph):
ChannelMessage.Read.All,ChannelMessage.SendChat.Read,Chat.ReadWrite,ChatMessage.SendTeam.ReadBasic.All,Channel.ReadBasic.AllUser.Read
- Click Grant admin consent (for your own tenant; other tenants consent on first login)
3. Configure & Deploy
cp .env.example .env
# Set TEAMS_CLIENT_ID, TEAMS_CLIENT_SECRET
# Set BASE_URL and REDIRECT_URI to your production URL
# TEAMS_AUTHORITY=common (multi-tenant, default)
Deploy to Railway, Render, Azure App Service, or any Node.js host:
# Railway
railway login && railway init && railway up
# Or Azure
az webapp up --name teams-mcp-server --runtime "NODE:20-lts"
# Or just run directly
TRANSPORT_MODE=http node dist/index.js
4. Submit to MCP Registry
Once deployed and tested, submit your server URL to Anthropic's MCP connector registry. Users will then see "Microsoft Teams" as a connect option in Claude Cowork — just like Slack and Gmail.
For Claude Code Users: Local STDIO Mode
Add to your .mcp.json:
{
"mcpServers": {
"teams": {
"command": "node",
"args": ["/path/to/teams-mcp-server/dist/index.js"],
"cwd": "/path/to/teams-mcp-server"
}
}
}
First run will open your browser for Microsoft login. After that, tokens are cached.
Available Tools
| Tool | What it does |
|---|---|
teams_list_teams | List all your Teams |
teams_list_channels | List channels in a team |
teams_read_channel_messages | Read recent channel messages |
teams_send_channel_message | Send a message to a channel |
teams_reply_to_message | Reply in a channel thread |
teams_read_message_replies | Read thread replies |
teams_list_chats | List your DMs and group chats |
teams_read_chat_messages | Read messages from a chat |
teams_send_chat_message | Send a direct/group chat message |
teams_search_messages | Search messages across all Teams |
teams_get_profile | Get your Microsoft 365 profile |
Architecture
src/
├── index.ts Main entry (auto-detects transport)
├── config.ts Central configuration
├── logger.ts Structured logging
├── types.ts TypeScript interfaces
├── sessions.ts Multi-user session manager
├── auth/
│ ├── oauth.ts MSAL OAuth (multi-tenant, per-user)
│ └── token-store.ts Persistent token cache
├── graph/
│ ├── client.ts Graph HTTP client with retries
│ ├── teams.ts Teams & channels API
│ ├── messages.ts Channel messages API
│ ├── chats.ts DM & group chat API
│ └── search.ts Search & profile API
├── mcp/
│ ├── server.ts MCP server factory
│ └── tools/ 11 tool definitions
├── transport/
│ ├── stdio.ts STDIO (Claude Code)
│ └── http.ts Express + SSE (Cowork / remote)
Environment Variables
| Variable | Required | Default | Description |
|---|---|---|---|
TEAMS_CLIENT_ID | Yes | — | Azure AD app client ID |
TEAMS_CLIENT_SECRET | Yes | — | Azure AD client secret |
TEAMS_AUTHORITY | No | common | common for multi-tenant, or a specific tenant ID |
TRANSPORT_MODE | No | auto | auto, stdio, or http |
PORT | No | 3000 | HTTP server port |
BASE_URL | No | http://localhost:3000 | Public URL |
REDIRECT_URI | No | {BASE_URL}/auth/callback | OAuth callback URL |
TOKEN_STORE_PATH | No | ./.data/tokens | Token cache directory |
LOG_LEVEL | No | info | Logging level |
License
MIT — LICENSE
Contributing
Issues and PRs welcome. Built by SurgeEnterpriseAI.
Frequently asked questions
What is Microsoft Teams?
Connect Claude to Microsoft Teams — read/send messages, list channels, search chats.
How do I install Microsoft Teams?
It runs on your machine. In Claude Code: claude mcp add microsoft-teams -- npx -y microsoft-teams-mcp-server@1.0.2. For other clients, paste the JSON configuration from this page into their MCP settings.
Does Microsoft Teams need an API key?
Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.
Is Microsoft Teams open source?
Yes. Its code is on GitHub under the MIT license.
Who maintains Microsoft Teams?
It is published by SurgeEnterpriseAI. AI.tn lists it but does not maintain or endorse it.
From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.