A
licenseA
qualityA
maintenanceAn MCP server for Microsoft Graph, exposing 60 tools across calendar, email, meetings, Teams chat, files, people, directory, tasks, and OneNote over stdio or Streamable HTTP.
23
36 PyPI
2
MIT
ms-teams-mcp
by Anupam890
Related Servers
Alternatives to ms-teams-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceMCP server that integrates Microsoft Teams messaging (read, post, mention, list members and threads)6399Apache 2.0
- AlicenseNot gradedqualityBmaintenanceMCP server for Microsoft Teams that lets AI assistants search, message, and manage chats, meetings, files, and contacts using your existing Teams browser login—no app approval or Azure AD registration needed.688 npmMIT
- FlicenseNot gradedqualityBmaintenanceMCP server providing access to Microsoft Teams chats/channels, Outlook emails, calendar events, and SharePoint files via Microsoft Graph API.-
- AlicenseAqualityBmaintenanceAn MCP server that provides comprehensive Microsoft Teams and Graph API access, enabling AI assistants to manage multi-tenant messaging, search, file operations, and user management.33MIT
- AlicenseAqualityBmaintenanceMCP server for Microsoft Outlook via Graph API. 20 consolidated tools for email, calendar, contacts, folders, rules, categories, and settings with safety controls (dry-run preview, rate limiting, recipient allowlists) and MCP annotations on every tool.822316 npm37MIT
TDQS
B3.2/5.0
Scored across 73 tools
Disambiguation4/5
Most tools target distinct resources and actions, but some overlap exists between similar operations like create_event vs create_user_event or list_shifts vs list_time_off vs list_time_off_requests. The large number of tools increases the chance of misselection, though descriptions generally clarify.
Naming Consistency5/5
All tool names follow a consistent verb_noun or verb_noun_noun pattern using snake_case (e.g., create_channel, list_team_members, send_channel_message). No mixing of conventions or vague verbs like 'process' or 'run'.
Tool Count3/5
With 73 tools, the server covers a wide range of Teams functionality, but the count feels slightly excessive for common use. While each tool serves a distinct purpose, a more focused subset could reduce complexity. Still within a reasonable range for a comprehensive integration.
Completeness4/5
The surface covers most CRUD operations for teams, channels, chats, messages, meetings, planner, shifts, time-off, apps, and tabs. Notable gaps include missing update operations for shifts and planner tasks, and no delete for chats or meetings. Overall, core workflows are well-supported.
Maintenance
ActivityInactive
ResponsivenessNo issues