A
licenseNot graded
qualityB
maintenanceMCP server that enables agents to interact with Microsoft Teams by listing channels and members, and asking humans questions, with replies routed back to the agent session.
MIT
MCP Microsoft Teams Server
by InditexTech
Related Servers
Alternatives to MCP Microsoft Teams Server
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceMCP server for Microsoft Teams that exposes 73 tools to manage teams, channels, chats, messages, meetings, planner, calendar, apps, tabs, scheduling, search, and authentication via the Graph API.7310 npmMIT
- 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 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.679 npm1MIT
- FlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that bridges Microsoft Teams with MCP-compatible clients (LLMs, agentic frameworks, CLI), enabling chat integration, message search, and event streaming without traditional REST API endpoints.-
- FlicenseNot gradedqualityBmaintenanceMCP server providing access to Microsoft Teams chats/channels, Outlook emails, calendar events, and SharePoint files via Microsoft Graph API.-
TDQS
A3.8/5.0
Scored across 6 tools
Disambiguation5/5
Each tool targets a distinct resource-action pair: thread lifecycle (start/update/read/list) and member lookup (get by name/list). There is no meaningful overlap, and the descriptions make the boundary between read_thread and list_threads clear.
Naming Consistency5/5
All tools follow a consistent snake_case verb_noun pattern such as start_, update_, read_, list_, and get_. The verb choices are predictable and match the operation being performed.
Tool Count5/5
Six tools is well-scoped for a Teams server covering thread management and member lookup. There are no redundant tools, and the set feels appropriately sized for its stated domain.
Completeness4/5
Threads have start, read, update, and list coverage, while members have get and list coverage. Missing thread deletion and explicit reply/send-message operations are minor gaps, but the core workflows agents would likely need are covered.
Maintenance
ActivityActive
ResponsivenessSlow