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 supports copy-paste install configs on its MCPpedia page for Claude Desktop, Cursor, and Claude Code. Scroll to the Quick Install section and select your client.

What can io.github.SurgeEnterpriseAI/teams-mcp-server do?

io.github.SurgeEnterpriseAI/teams-mcp-server provides 11 tools: teams_list_teams, teams_list_channels, teams_read_channel_messages, teams_send_channel_message, teams_reply_to_message and 6 more. See the full tools list on the server page for descriptions and parameters.

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. It uses stdio and sse and http transport.

Is io.github.SurgeEnterpriseAI/teams-mcp-server actively maintained?

io.github.SurgeEnterpriseAI/teams-mcp-server is recently maintained — last commit was 82 days ago. It has 1 GitHub stars.

io.github.SurgeEnterpriseAI/teams-mcp-server

npm

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

1 14.9M/wk 11 tools GitHub npm

No known CVEs

No license

Maintained

Last commit 82d ago

Works with most clients

Transport: stdio, sse, http

11 tools · ~807 tok

Grade B · 0.4% of 200K ctx

Edit this pageView history

Communication

Step 1

Install in your client

Config is the same across clients — only the file and path differ.

Supported in Claude Desktopstdio, sse, http · Node 18+

Paste into ~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "teams": {
      "cwd": "/path/to/teams-mcp-server",
      "args": [
        "/path/to/teams-mcp-server/dist/index.js"
      ],
      "command": "node"
    }
  }
}

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)

Read me

What io.github.SurgeEnterpriseAI/teams-mcp-server does

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.

Test This Server

Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.

npx -y 'npm' 2>&1 | head -1 && echo "✓ Server started successfully"

After testing, let us know if it worked:

Loading README…

Scored, not listed

Why this score

Five weighted categories — click any category to see the underlying evidence.

Score breakdown

83/100across 5 weighted dimensions

How we score →

0255075100

−17

Security

Maintenance

Efficiency

Documentation

Compatibility

Categoriesclick a row to see evidence

Security

OSV.dev

8 fixed

CVE-2022-29244high · fixedCVSS 7.5

Packing does not respect root-level ignore files in workspaces

### Impact `npm pack` ignores root-level `.gitignore` & `.npmignore` file exclusion directives when run in a workspace or with a workspace flag (ie. `--workspaces`, `--workspace=<name>`). Anyone who has run `npm pack` or `npm publish` with workspaces, as of [v7.9.0](https://github.com/npm/cli/releases/tag/v7.9.0) & [v7.13.0](https://github.com/npm/cli/releases/tag/v7.13.0) respectively, may be affected and have published files into the npm registry they did not intend to include. ### Patch - Up

Affected: >= 7.9.0Fixed in 8.11.0source →

CVE-2018-7408high · fixedCVSS 7.8

Incorrect Permission Assignment for Critical Resource in NPM

An issue was discovered in an npm 5.7.0 2018-02-21 pre-release (marked as "next: 5.7.0" and therefore automatically installed by an "npm upgrade -g npm" command, and also announced in the vendor's blog without mention of pre-release status). It might allow local users to bypass intended filesystem access restrictions because ownerships of /etc and /usr directories are being changed unexpectedly, related to a "correctMkdir" issue.

Affected: >= 0Fixed in 5.7.1source →

CVE-2013-4116info · fixed

Local Privilege Escalation in npm

Affected versions of `npm` use predictable temporary file names during archive unpacking. If an attacker can create a symbolic link at the location of one of these temporary file names, the attacker can arbitrarily write to any file that the user which owns the `npm` process has permission to write to, potentially resulting in local privilege escalation. ## Recommendation Update to version 1.3.3 or later.

Affected: >= 0Fixed in 1.3.3source →

CVE-2020-15095medium · fixedCVSS 4.4

npm CLI exposing sensitive information through logs

Versions of the npm CLI prior to 6.14.6 are vulnerable to an information exposure vulnerability through log files. The CLI supports URLs like `<protocol>://[<user>[:<password>]@]<hostname>[:<port>][:][/]<path>`. The password value is not redacted and is printed to stdout and also to any generated log files.

Affected: >= 0Fixed in 6.14.6source →

CVE-2019-16777high · fixedCVSS 7.7

npm Vulnerable to Global node_modules Binary Overwrite

Versions of the npm CLI prior to 6.13.4 are vulnerable to a Global node_modules Binary Overwrite. It fails to prevent existing globally-installed binaries to be overwritten by other package installations. For example, if a package was installed globally and created a `serve` binary, any subsequent installs of packages that also create a `serve` binary would overwrite the first binary. This will not overwrite system binaries but only binaries put into the global node_modules directory. This b

Affected: >= 0Fixed in 6.13.4source →

Inventory

Tools (11)

Click any tool to inspect its schema.

~807 tokens total

Community

Reviews

Be the first to review

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 supports copy-paste install configs on its MCPpedia page for Claude Desktop, Cursor, and Claude Code. Scroll to the Quick Install section and select your client.
What can io.github.SurgeEnterpriseAI/teams-mcp-server do?: io.github.SurgeEnterpriseAI/teams-mcp-server provides 11 tools: teams_list_teams, teams_list_channels, teams_read_channel_messages, teams_send_channel_message, teams_reply_to_message and 6 more. See the full tools list on the server page for descriptions and parameters.
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. It uses stdio and sse and http transport.
Is io.github.SurgeEnterpriseAI/teams-mcp-server actively maintained?: io.github.SurgeEnterpriseAI/teams-mcp-server is recently maintained — last commit was 82 days ago. It has 1 GitHub stars.

Similar servers

Others in communication

View all →

Mcp_agent_mail96

Asynchronous coordination layer for AI coding agents: identities, inboxes, searchable threads, and advisory file leases over FastMCP + Git + SQLite

2.0k 6

io.github.VibeCodingInc/vibe-mcp89

Social layer for Claude Code - DMs, presence, discovery, and games between AI-assisted developers

io.github.alexkirienko/safebot-chat89

End-to-end encrypted multi-agent chat rooms. Client-side crypto; zero chat logs.

1 5

Server88

PubNub Model Context Protocol MCP Server for Cursor and Claude

31 2

MCP Security Weekly

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

Community

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?

Edit this pageView history

Communication

Step 1

Install in your client

Config is the same across clients — only the file and path differ.

Supported in Claude Desktopstdio, sse, http · Node 18+

Paste into ~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "teams": {
      "cwd": "/path/to/teams-mcp-server",
      "args": [
        "/path/to/teams-mcp-server/dist/index.js"
      ],
      "command": "node"
    }
  }
}

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)

Read me

What io.github.SurgeEnterpriseAI/teams-mcp-server does

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.

Test This Server

Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.

npx -y 'npm' 2>&1 | head -1 && echo "✓ Server started successfully"

After testing, let us know if it worked:

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)

Loading README…

Scored, not listed

Why this score

Five weighted categories — click any category to see the underlying evidence.

Score breakdown

83/100across 5 weighted dimensions

How we score →

0255075100

−17

Security

Maintenance

Efficiency

Documentation

Compatibility

Categoriesclick a row to see evidence

Security

OSV.dev

8 fixed

CVE-2022-29244high · fixedCVSS 7.5

Packing does not respect root-level ignore files in workspaces

Affected: >= 7.9.0Fixed in 8.11.0source →

CVE-2018-7408high · fixedCVSS 7.8

Incorrect Permission Assignment for Critical Resource in NPM

Affected: >= 0Fixed in 5.7.1source →

CVE-2013-4116info · fixed

Local Privilege Escalation in npm

Affected: >= 0Fixed in 1.3.3source →

CVE-2020-15095medium · fixedCVSS 4.4

npm CLI exposing sensitive information through logs

Affected: >= 0Fixed in 6.14.6source →

CVE-2019-16777high · fixedCVSS 7.7

npm Vulnerable to Global node_modules Binary Overwrite

Affected: >= 0Fixed in 6.13.4source →

Inventory

Tools (11)

Click any tool to inspect its schema.

~807 tokens total

Community

Reviews

Be the first to review

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 supports copy-paste install configs on its MCPpedia page for Claude Desktop, Cursor, and Claude Code. Scroll to the Quick Install section and select your client.
What can io.github.SurgeEnterpriseAI/teams-mcp-server do?: io.github.SurgeEnterpriseAI/teams-mcp-server provides 11 tools: teams_list_teams, teams_list_channels, teams_read_channel_messages, teams_send_channel_message, teams_reply_to_message and 6 more. See the full tools list on the server page for descriptions and parameters.
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. It uses stdio and sse and http transport.
Is io.github.SurgeEnterpriseAI/teams-mcp-server actively maintained?: io.github.SurgeEnterpriseAI/teams-mcp-server is recently maintained — last commit was 82 days ago. It has 1 GitHub stars.