A
licenseA
qualityD
maintenanceEnables interaction with Microsoft Teams chats and channels using official Microsoft Graph API or Power Automate for enterprise environments with restricted permissions.
9
1
MIT
mcp-teams
by dockndevai
Related Servers
Alternatives to mcp-teams
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to interact with Microsoft Teams, users, and organizational data via Microsoft Graph APIs, including sending messages, managing chats and channels, and searching messages.MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to manage Microsoft Teams through the Graph API, including sending messages, managing chats, creating teams, and searching communications.MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to read conversations, send messages, and manage members in Microsoft Teams via the Teams Chat Service REST API.291 npm8MIT
- AlicenseAqualityDmaintenanceEnables AI agents to interact with Microsoft Teams through Microsoft Graph API, using delegated device-code authentication to act on behalf of the user.1631 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables authenticated interaction with Microsoft 365 and Office services through the Graph API, covering email, calendar, files, Teams, SharePoint, and more. Supports read-only mode, tool filtering, presets, and multiple cloud environments for safe, controlled access.54,304 npmMIT
TDQS
A4.1/5.0
Scored across 9 tools
Disambiguation5/5
Each tool targets a distinct Teams entity and action: identity, teams, channels, members, channel messages, replies, and chats. The potentially similar message tools are clearly separated by scope (channel vs. chat vs. reply) and by singular vs. plural retrieval.
Naming Consistency4/5
The naming is overwhelmingly consistent with a list_* / get_* verb-noun pattern. The main deviation is whoami, which is a common standard command, and the distinction between list and get is semantically clear.
Tool Count5/5
Nine tools is well-scoped for a read-only Microsoft Teams server. Every tool earns its place by covering a distinct read operation without unnecessary redundancy or bloat.
Completeness4/5
Core read workflows are covered well: identity, teams, channels, members, channel messages with replies, and chats. The main gaps are the lack of a full get_chat_message equivalent, no search capability, and no write actions, but these are workable for a listing-focused server.
Maintenance
ActivityMaintained
ResponsivenessNo issues