MS 365-21V MCP Server
Related Servers
Alternatives to MS 365-21V MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables MCP-compatible AI clients to query and act on a user's 21Vianet Microsoft 365 data, including mail, calendar, OneDrive, SharePoint, Teams, contacts, and Microsoft Search, through Microsoft Graph in China under delegated permissions. It supports OAuth login, module/scope filtering, write-operation confirmation, and auditing boundaries.MIT
- AlicenseNot gradedqualityAmaintenanceEnables MCP-capable AI clients to access 21Vianet Microsoft 365 mail, calendar, OneDrive, SharePoint, Teams, contacts, and search as the signed-in user through Microsoft Graph China. It preserves user permissions and supports OAuth, tool filtering, operation confirmation, and audit boundaries.MIT
- FlicenseNot gradedqualityAmaintenanceEnables MCP-capable AI clients to access and manage a user's 21Vianet Microsoft 365 mail, calendar, OneDrive, SharePoint, Teams, contacts, org users, and search through Microsoft Graph China, while respecting delegated permissions, confirmations, and audit boundaries.-
- FlicenseNot gradedqualityAmaintenanceEnables MCP-compatible AI clients to access 21Vianet Microsoft 365 mail, calendar, OneDrive, SharePoint, Teams, contacts, and other Microsoft Graph China resources as the signed-in user, with delegated permissions, operation confirmation, and audit controls.-
- AlicenseNot gradedqualityAmaintenanceEnables MCP-capable AI clients to access and act on a user's 21Vianet Microsoft 365 resources—mail, calendar, OneDrive, SharePoint, Teams, contacts, and search—via Microsoft Graph China while preserving delegated permissions, confirmations, and audit boundaries.MIT
- FlicenseNot gradedqualityAmaintenanceEnables MCP-capable AI clients to access 21Vianet-operated Microsoft 365 resources — mail, calendar, OneDrive, SharePoint, Teams, contacts, org users and search — through the China-region Microsoft Graph using per-user OAuth delegated permissions. It supports client connectivity over Streamable HTTP with an OAuth bridge, plus module/scope filtering, write-operation confirmation and desensitized auditing.-
TDQS
Scored across 16 tools
Most tools target distinct resources and actions (mail_list/search/get, teams_list_chats vs teams_list_chat_messages, auth_* lifecycle). The only mild overlap is gateway_search_tools already returning schemas while gateway_get_tool_schema exists for explicit schema retrieval, and gateway_execute_tool vs confirm_execute for executing operations, but descriptions clarify the boundaries.
Names follow a predictable domain_verb_noun snake_case pattern (mail_list_messages, calendar_list_view, files_get_download_url, gateway_search_tools). Minor deviations like auth_status (noun-only) and confirm_execute (no domain prefix) are readable and don't break the overall convention.
16 tools is slightly above the ideal 3-15 range but well justified by the breadth of Microsoft 365 domains covered (auth, mail, calendar, files, teams, gateway). The gateway pattern lets a small curated set extend to a long tail without bloating the direct surface.
Core read workflows are fully covered per domain (mail list/search/get, calendar list view, files search/download, teams chats/messages) plus a complete auth lifecycle. Write operations (send mail, create calendar events, upload files) are not directly exposed but are discoverable and executable through gateway_search_tools/gateway_execute_tool, so only minor gaps remain.