cipp-mcp
Related Servers
Alternatives to cipp-mcp
No user-submitted related servers found.
Related Servers
- 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.3338 npmMIT
- AlicenseNot gradedqualityBmaintenanceAn MCP server for Blackpoint Cyber MDR platform, enabling management of security monitoring, threat detection, and incident response through Blackpoint's API.Apache 2.0
- FlicenseNot gradedqualityDmaintenanceAn MCP server for Microsoft 365 administration using the Microsoft Graph API, enabling user, group, and mailbox management.-
- AlicenseAqualityBmaintenanceAn MCP server for Action1, a cloud-native RMM platform, enabling remote monitoring, patch management, and endpoint management through Action1's API.65Apache 2.0
- AlicenseNot gradedqualityBmaintenanceAn MCP server for Datto BCDR (Business Continuity and Disaster Recovery), enabling management of backup jobs, restore points, and disaster recovery operations through Datto's API.Apache 2.0
- AlicenseAqualityBmaintenanceAn MCP server for SuperOps PSA/RMM, enabling MSPs to manage tickets, assets, clients, and field technician operations through SuperOps's API.273Apache 2.0
TDQS
Scored across 49 tools
Most tools target distinct resource+action pairs, and the long descriptions actively disambiguate close pairs (cipp_list_mailbox_usage vs cipp_get_mailbox_usage, cipp_get_secure_score vs cipp_list_secure_score_controls, cipp_get_tenant_drift vs cipp_get_tenant_alignment). The remaining friction is in the user-signal cluster (cipp_list_users, cipp_list_mfa_users, cipp_list_user_signin_logs) and the log family (cipp_list_logs vs cipp_list_audit_logs), which an agent could still mis-pick without reading carefully.
Nearly everything follows a uniform cipp_<verb>_<noun> snake_case pattern with no case mixing. Minor deviations exist: cipp_bec_check inverts to noun_verb, and cipp_ping / cipp_get_version lack a resource noun, but these are few and still readable.
49 tools is heavy for a single server, sitting just under the point where the surface becomes unmanageable. The breadth is partly earned — tenant admin, user lifecycle, mailbox, groups, GDAP, standards, secure score, scheduling, and logging are genuinely distinct domains — but it is still well past a comfortable scope.
Read coverage is broad and the write surface covers most high-risk user actions (create, edit, disable, reset password/MFA, revoke sessions, offboard). However, there are notable dead ends: disable_user has no matching enable/re-enable tool, groups can be created but not deleted or modified, and scheduled items can be added but not edited or removed.