Related Servers

Most tools target a clearly distinct resource+action, and the few genuinely close pairs (cipp_list_mailbox_usage vs cipp_get_mailbox_usage, cipp_list_licenses vs cipp_list_csp_licenses, cipp_list_logs vs cipp_list_audit_logs, cipp_get_secure_score vs cipp_list_secure_score_controls) have descriptions that explicitly state when to use which. That leaves little room for misselection, though the density of similarly named list_* tools means an agent must read descriptions carefully rather than pick by name alone.

The set is overwhelmingly consistent snake_case with a cipp_ prefix plus a verb_noun shape (list_users, get_tenant_details, create_group, reset_password). Minor deviations exist: creation uses both 'create_' and 'add_' (cipp_add_scheduled_item vs cipp_create_user), and cipp_ping / cipp_bec_check don't follow verb_noun. These are readable and predictable overall.

49 tools is heavy for a single MCP surface, and the server is dominated by one-shot read tools (list_*) for many narrow report types. Even granting the broad MSP/multi-tenant M365 domain, the set would be easier to route with consolidation (e.g. fewer list_* variants) or grouping, so it sits well past the 'feels heavy' 16-25 band.

Read coverage is genuinely broad (identity, mail, security score, standards, GDAP, audit, domains), and high-impact writes are thoughtfully gated. But lifecycle coverage is uneven: scheduled items can only be added/listed (no edit, delete, or run), groups and mailboxes have no membership/permission modification, there is no delete_user or unassign-license path, and standards templates lack a get-details tool. Agents will hit dead ends on common admin follow-ups.