Skip to main content
Glama
WYRE-AI

cipp-mcp

by WYRE-AI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to cipp-mcp

No user-submitted related servers found.

    Related Servers

    • Teams MCP Plus

      stackia
      A
      license
      A
      quality
      B
      maintenance
      An 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.
      33
      32 npm
      MIT

    • blackpoint-mcp

      WYRE-AI
      A
      license
      Not graded
      quality
      A
      maintenance
      An MCP server for Blackpoint Cyber MDR platform, enabling management of security monitoring, threat detection, and incident response through Blackpoint's API.
      Apache 2.0

    • action1-mcp

      WYRE-AI
      A
      license
      A
      quality
      A
      maintenance
      An MCP server for Action1, a cloud-native RMM platform, enabling remote monitoring, patch management, and endpoint management through Action1's API.
      6
      3
      Apache 2.0

    • datto-bcdr-mcp

      WYRE-AI
      A
      license
      Not graded
      quality
      A
      maintenance
      An 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

    • superops-mcp

      WYRE-AI
      A
      license
      A
      quality
      A
      maintenance
      An MCP server for SuperOps PSA/RMM, enabling MSPs to manage tickets, assets, clients, and field technician operations through SuperOps's API.
      22
      3
      Apache 2.0
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.1/5.0

    Scored across 47 tools

    Disambiguation4/5

    Most tools target a clearly distinct resource and action, and descriptions explicitly differentiate near-pairs like cipp_list_mailbox_usage vs cipp_get_mailbox_usage. However, cipp_list_standard_templates vs cipp_list_standards and cipp_get_tenant_drift vs cipp_get_tenant_alignment could still be confused by an agent without close reading.

    Naming Consistency4/5

    All tools use the cipp_ prefix and snake_case verb-first names, predominantly list/get/create/set/run, so the pattern is easy to follow. Minor deviations like cipp_ping and cipp_bec_check are readable but keep this from being perfectly uniform.

    Tool Count2/5

    At 47 tools, this is well beyond the 3-15 sweet spot and into the 25+ range that burdens tool selection. Even for a broad M365 management platform, many read-only list tools could be consolidated or selectively exposed.

    Completeness3/5

    The surface has broad read coverage and some high-impact writes (user create/edit/disable/reset/offboard, group create, standards templates, OOO/forwarding). But many resources lack full lifecycle: no user delete, no group update/delete, no Conditional Access write, no GDAP invite management, no license assignment, and mailbox permissions remain read-only.

    Maintenance

    ActivityActive
    ResponsivenessResponsive

    Resources