graph-atlas-mcp
Related Servers
Alternatives to graph-atlas-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceA Model Context Protocol server for Microsoft 365 administration using Graph API application permissions, enabling security monitoring, identity audits, incident response, and service health management.88 npm18MIT
- FlicenseNot gradedqualityBmaintenanceMCP server providing access to Microsoft Teams chats/channels, Outlook emails, calendar events, and SharePoint files via Microsoft Graph API.-
- AlicenseAqualityBmaintenanceMCP server for Microsoft 365 via the Microsoft Graph API, providing read-only access to profile, calendar, email, Teams chats, OneDrive files, and meeting transcripts from any MCP client.1612 npm3MIT
- FlicenseNot gradedqualityBmaintenanceA Model Context Protocol (MCP) server for interacting with Microsoft 365 and Microsoft Office services through the Graph API.-
- AlicenseNot gradedqualityDmaintenanceAn 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
- AlicenseCqualityAmaintenanceA 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.48MIT
TDQS
Scored across 12 tools
The change-history cluster (search_changes, get_recent_changes, get_object_history, get_node_timeline, get_change_detail) has real overlap, but descriptions clearly separate natural-language search, filtered recent queries, per-object history, compact visualizer timeline, and single-record detail. schema_change_report and visualize_schema_graph intentionally expose the same data with and without rendering, which is explained but still a potential source of confusion.
Most tools follow a predictable verb_noun pattern (search_changes, get_object_history, expand_schema_node, visualize_schema_graph). schema_change_report is noun-only, a minor deviation in an otherwise consistent set.
Twelve tools is well within a healthy range and each serves a distinct role: change discovery, detail/history, snapshot metadata, permission reasoning, visualization, and server info. No obvious filler tools.
The surface covers change search, filtering, history, detail, snapshot summaries, permissions/roles, schema exploration, and visualizer support quite thoroughly. Minor gaps exist around explicit snapshot/release listing and change diffing between snapshots, though get_server_info and get_snapshot_summary partially mitigate these.