* fix: pin npm package versions in MCP integration templates Prevent supply chain attacks by pinning exact versions instead of using unpinned `npx -y @package` which pulls latest on every run. 23 of 25 integrations pinned. sqlite-mcp and aws skipped (packages not found on npm registry). * fix: use stable azure/mcp version instead of beta
28 lines
909 B
TOML
28 lines
909 B
TOML
id = "teams-mcp@0.3.3"
|
|
name = "Microsoft Teams"
|
|
description = "Access Microsoft Teams channels, chats, and messages through the MCP server"
|
|
category = "communication"
|
|
icon = "👥"
|
|
tags = ["chat", "messaging", "microsoft", "enterprise", "collaboration"]
|
|
|
|
[transport]
|
|
type = "stdio"
|
|
command = "npx"
|
|
args = ["-y", "teams-mcp@0.3.3"]
|
|
|
|
[oauth]
|
|
provider = "microsoft"
|
|
scopes = ["Team.ReadBasic.All", "Chat.ReadWrite"]
|
|
auth_url = "https://login.microsoftonline.com/common/oauth2/v2.0/authorize"
|
|
token_url = "https://login.microsoftonline.com/common/oauth2/v2.0/token"
|
|
|
|
[health_check]
|
|
interval_secs = 60
|
|
unhealthy_threshold = 3
|
|
|
|
setup_instructions = """
|
|
1. Click 'Connect' to initiate the OAuth flow with your Microsoft account.
|
|
2. Sign in with your Microsoft 365 account and grant LibreFang permission to read teams and read/write chats.
|
|
3. The connection will be established automatically after authorization.
|
|
"""
|