Microsoft Teams MCP Server
Related Servers
Alternatives to Microsoft Teams MCP Server
No user-submitted related servers found.
Related Servers
- 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-
- AlicenseNot gradedqualityFmaintenanceA TypeScript-based MCP server that enables AI agents to send messages to Microsoft Teams channels via incoming webhooks. It also includes a ping tool for health checks and connection verification.2,105 npmApache 2.0
- AlicenseAqualityBmaintenanceMCP server that integrates Microsoft Teams messaging (read, post, mention, list members and threads)6467Apache 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-
- AlicenseNot gradedqualityBmaintenanceThis MCP server enables sending notifications, images, files and typing indicators to your own WeChat account through an iLink Bot, exposing a single send_wechat_message tool over Streamable HTTP. It helps deliver build results, task progress or alerts to yourself, with a local admin page for managing tokens and chat history.MIT
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.