Microsoft Teams MCP Server
microsoft-teams-mcp MCP 服务器
带有 Microsoft Teams 聊天通知工具的 MCP 服务器。
[!警告]
这仅供参考,并未使用 VS Code 以外的 MCP 客户端进行测试。
成分
工具
服务器实现了一个工具:
send-notification:向 Microsoft Teams 发送通知消息
将“消息”和“项目”作为必需的字符串参数
支持 Markdown 格式的消息
使用 Azure AD 身份验证与 Teams 进行安全通信
Related MCP server: Toast MCP Server
配置
这需要使用 Microsoft Teams 机器人来发送通知。您可以使用我使用Teams Toolkit创建的示例通知机器人。
服务器需要设置以下环境变量:
BOT_ENDPOINT:你的 Microsoft Teams 机器人的 URL 端点MICROSOFT_APP_ID:来自 Azure AD 应用注册的应用程序(客户端)IDMICROSOFT_APP_PASSWORD:来自 Azure AD 应用注册的客户端机密MICROSOFT_APP_TENANT_ID:您的 Azure AD 租户 IDEMAIL:接收通知的用户的电子邮件地址
您可以在项目根目录中的.env文件中设置这些。
快速入门
安装
VS 代码
这是使用 VS Code 中的 MCP 支持进行的测试,在创建时仅在 VS Code Insiders 中可用。
将其添加到 VS Code Insiders 设置(JSON)
"mcp": {
"inputs": [],
"servers": {
"MicrosoftTeams": {
"command": "uv",
"args": [
"--directory",
"<path/to/the/project>/microsoft-teams-mcp",
"run",
"microsoft-teams-mcp"
],
"env": {
"BOT_ENDPOINT": "<endpoint or dev tunnel URL of Teams bot>/api/notification",
"MICROSOFT_APP_ID": "<microsoft-entra-client-id>",
"MICROSOFT_APP_PASSWORD": "<microsoft-entra-client-secret>",
"MICROSOFT_APP_TENANT_ID": "<microsoft-entra-tenant-id>",
"EMAIL": "<your-email-in-teams>",
}
}
}
}发展
建筑
准备分发包:
同步依赖项并更新锁文件:
uv sync构建软件包分发版:
uv buildAvailable Tools
1 toolsend-notificationC
Send a notification message to the user. Supports markdown formatting for messages. Use backticks for code blocks and inline code. Use square brackets for placeholders.
Inputs: message (required), project (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The tool 'send-notification' has a clear and singular purpose, making it impossible for an agent to misselect between tools.
The single tool name 'send-notification' follows a consistent verb-noun pattern. Since there is only one tool, there is no inconsistency to evaluate, and the naming is straightforward and predictable.
A single tool is too few for a server named 'Microsoft Teams MCP Server', which suggests a broader domain like messaging, collaboration, or team management. This minimal set likely leaves significant gaps in functionality, making it inappropriate for the implied scope.
The tool set is severely incomplete for a Microsoft Teams server. It only covers sending notifications, missing essential operations such as reading messages, managing channels, handling meetings, or interacting with users, which are core to the Teams domain and will cause agent failures.
Maintenance
Related MCP Connectors
The MCP server for Azure DevOps, bringing the power of Azure DevOps directly to your agents.
One MCP server for all your MCP servers: code mode, per-tool permissions, approvals and audit.
Build your own tools from chat: design, test and host them on a shareable MCP server URL.
One MCP server for all your work accounts: Slack, Teams, Google Chat, Jira, ClickUp, digest, tasks.
Related MCP Servers
- AlicenseAqualityBmaintenanceMCP server that integrates Microsoft Teams messaging (read, post, mention, list members and threads)6469Apache 2.0
- AlicenseNot gradedqualityDmaintenanceAn MCP server that displays desktop notifications on Windows 10 and macOS, compatible with VSCode Cline and supporting customizable notification parameters.4MIT
- FlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that bridges Microsoft Teams and MCP-compatible clients, enabling chat integration, message handling, and advanced search capabilities without REST API endpoints.1-
- FlicenseNot gradedqualityNot gradedmaintenanceAn MCP server that enables sending data to webhooks via HTTP POST for both local and remote team environments. It provides a tool for relaying task descriptions, custom metadata, and automated notifications to external services.4 npm-