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

    • 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
      2
      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.
      21
      3
      Apache 2.0
    • immybot-mcp by WYRE-AI

      immybot-mcpofficial

      WYRE-AI
      F
      license
      Not graded
      quality
      B
      maintenance
      An MCP server for ImmyBot IT automation platform, enabling management of computers, deployments, software, and maintenance sessions through ImmyBot's API.
      -
    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 45 tools

    Disambiguation4/5

    Most tools follow a clear resource/action mapping, so list_tenants, create_user, reset_mfa, and get_tenant_drift are easy to tell apart. A few pairs require reading the descriptions to distinguish—notably list_mailbox_usage vs get_mailbox_usage, list_groups vs list_user_groups, and the standards/alignment/drift cluster—but the descriptions resolve the ambiguity.

    Naming Consistency4/5

    The cipp_ prefix plus lowercase snake_case verbs is consistent throughout, and most names use a verb_noun pattern. Minor deviations such as cipp_bec_check instead of cipp_run_bec_check and cipp_add_scheduled_item alongside cipp_create_group prevent a perfect score.

    Tool Count2/5

    45 tools is well above the 25+ threshold that makes a tool set heavy to navigate. The broad Microsoft 365/CIPP domain justifies some size, but the count will still burden an agent's selection and context window.

    Completeness3/5

    The surface covers many important CIPP workflows: user lifecycle, mailbox diagnostics, standards/BPA, security checks, licensing, and tenant details. However, there are notable gaps such as no group deletion/member management, no delete or edit for scheduled items, no GDAP invite creation, and no mailbox permission changes, which agents cannot work around without leaving the server.

    Maintenance

    ActivityActive
    ResponsivenessResponsive

    Resources