Skip to main content
Glama

Related Servers

Alternatives to graph-atlas-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      A
      maintenance
      A Model Context Protocol server for Microsoft 365 administration using Graph API application permissions, enabling security monitoring, identity audits, incident response, and service health management.
      85 npm
      12
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that integrates with Microsoft Defender for Identity via the Microsoft Graph API, enabling natural language queries and HTML report generation for alerts, incidents, risky users, and more.
      MIT
    • A
      license
      B
      quality
      C
      maintenance
      A FastMCP server for interacting with Microsoft Entra ID via the Microsoft Graph API, enabling management of users, groups, sign-in logs, MFA, applications, devices, conditional access, and more.
      48
      MIT

    TDQS

    A3.8/5.0

    Scored across 12 tools

    Disambiguation3/5

    Several tools have overlapping surfaces: search_changes, get_recent_changes, get_object_history, and get_node_timeline all return change-related data, and schema_change_report, visualize_schema_graph, and expand_schema_node all expose schema graph views. Descriptions are detailed enough to usually disambiguate, but an agent could struggle to choose between get_permission_context and the permission/role views of schema_change_report or expand_schema_node.

    Naming Consistency4/5

    Most tools follow a clear get_/search_/visualize_/expand_ pattern: get_recent_changes, get_object_history, search_schema_objects, etc. The outlier is schema_change_report, which uses a noun-noun form and doesn't fit the verb-prefix convention. Overall the naming is predictable and readable, with only minor deviation.

    Tool Count5/5

    12 tools is well within the ideal range for a specialized server. Each tool serves a distinct role in the workflow—searching, querying, drilling down, visualizing, and schema exploration—without feeling padded or redundant.

    Completeness5/5

    The tool surface covers the full journey from natural-language discovery through structured filters, object history, permission context, snapshot metadata, schema graph exploration/reporting, and visual interaction. No obvious dead ends: search_results can lead to detail tools, schema searches feed visualization/expansion, and server freshness is checkable. The domain appears fully covered for a read-only Graph API atlas.

    Maintenance

    ActivityActive
    ResponsivenessUnresponsive