Is io.github.SurgeEnterpriseAI/teams-mcp-server safe to use?

io.github.SurgeEnterpriseAI/teams-mcp-server has no known CVEs as of the latest MCPpedia security scan. It does not require authentication, so any local process can connect — keep this in mind in shared environments.

How do I install io.github.SurgeEnterpriseAI/teams-mcp-server?

io.github.SurgeEnterpriseAI/teams-mcp-server can be installed by cloning its GitHub repository and following the setup instructions in the README.

io.github.SurgeEnterpriseAI/teams-mcp-server

Connect Claude to Microsoft Teams — read/send messages, list channels, search chats.

UnknownNot tested

AI / ML Productivity

GitHub

16FNo CVEsunknown

Quick Install

{
  "mcpServers": {
    "io-github-surgeenterpriseai-teams-mcp-server": {
      "command": "<see-readme>",
      "args": []
    }
  }
}

Setup guide

No install config available. Check the server's README for setup instructions.

Are you the author?

Add this badge to your README to show your security score and help users find safe servers.

Embed in your READMEAbout badges →

[![MCPpedia Score](https://mcppedia.org/api/badge/io-github-surgeenterpriseai-teams-mcp-server)](https://mcppedia.org/s/io-github-surgeenterpriseai-teams-mcp-server)

Should you use this server?

Connect Claude to Microsoft Teams — read/send messages, list channels, search chats.

✓

Is it safe?

No package registry to scan.

No authentication — any process on your machine can connect.

License not specified.

Is it maintained?

Commit history unknown.

Will it work with my client?

Transport: stdio. Works with Claude Desktop, Cursor, Claude Code, and most MCP clients.

README

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.Send
- Chat.Read, Chat.ReadWrite, ChatMessage.Send
- Team.ReadBasic.All, Channel.ReadBasic.All
- User.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/

... [View full README on GitHub](https://github.com/SurgeEnterpriseAI/teams-mcp-server#readme)

Test This Server

No automated test available for this server. Check the GitHub README for setup instructions.

Help improve this page

This server is missing a description. Tools and install config are also missing.If you've used it, help the community.

Add information

Score Breakdown

MCPpedia Score

Click each category to see evidence

16F

Last scored 2h ago

How we score →

Security

3/30

No known vulnerabilities.

○

Known CVEs — No package registry to scan

○

Tool safety — No tools to analyze

○

Tool poisoning — No tools to analyze

○

Injection vectors — No tools to analyze

✓

Tool stability — Tool definitions stable

○

Dependency health — No package to analyze

✗

License — No license specified

○

Authentication — No authentication required

○

Repository — active repo

CVEs checked daily via OSV.dev. Score algorithm is open source.

Reviews

Have you used this server?

Share your experience — it helps other developers decide.

How easy was setup?Did it work reliably?How was the documentation?

Frequently Asked Questions

Is io.github.SurgeEnterpriseAI/teams-mcp-server safe to use?: io.github.SurgeEnterpriseAI/teams-mcp-server has no known CVEs as of the latest MCPpedia security scan. It does not require authentication, so any local process can connect — keep this in mind in shared environments.
How do I install io.github.SurgeEnterpriseAI/teams-mcp-server?: io.github.SurgeEnterpriseAI/teams-mcp-server can be installed by cloning its GitHub repository and following the setup instructions in the README.
What AI clients work with io.github.SurgeEnterpriseAI/teams-mcp-server?: io.github.SurgeEnterpriseAI/teams-mcp-server is compatible with Claude Desktop, Cursor, Claude Code, and most MCP clients that support stdio transport. It uses stdio transport.

Similar servers

View all →

Sequential Thinking MCP Server

Official

No CVEs98A

Dynamic problem-solving through sequential thought chains

1 toolsstdio83.8k111.0k/wk23h ago

XcodeBuildMCP

Official

No CVEs97A

A Model Context Protocol (MCP) server and CLI that provides tools for agent use when working on iOS and macOS projects.

2 toolsremote5.2k46.6k/wk1d ago

Scrumboy

No CVEs95A

a self-hosted project management & Kanban solution + Instant shareable boards

1 toolsremote167601.9k/wk21h ago

Python Sdk

Official

No CVEs95A

The official Python SDK for Model Context Protocol servers and clients

1 toolsremote22.6k156.5k/wk16h ago

MCP Security Weekly

Get CVE alerts and security updates for io.github.SurgeEnterpriseAI/teams-mcp-server and similar servers.

Discussion

Start a conversation

Ask a question, share a tip, or report an issue.

Has anyone used this with Cursor?How do you handle auth?Any alternatives?

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       │  │
                                         │  └────────────────┘  │
                                         └──────────────────────┘

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.Send
- Chat.Read, Chat.ReadWrite, ChatMessage.Send
- Team.ReadBasic.All, Channel.ReadBasic.All
- User.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/

... [View full README on GitHub](https://github.com/SurgeEnterpriseAI/teams-mcp-server#readme)