Skip to main content
Glama
josimarh

azure-mcp-pilot

by josimarh

Related Servers

Alternatives to azure-mcp-pilot

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      Enables security analysts to investigate Microsoft Entra ID security logs through natural language, exposing read-only tools for user context, sign-ins, risky users, risk detections, directory audits, and conditional access policies.
      6
      MIT
    • -
      license
      Not graded
      quality
      Not graded
      maintenance
      Provides secure access to Microsoft Entra ID (Azure AD) resources including users, devices, and applications through Microsoft Graph API. Enables querying organizational data with comprehensive audit logging to Azure Blob Storage.
      -
    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to inspect and audit Azure Landing Zones by inventorying resources, auditing tagging, evaluating policy compliance, and detecting infrastructure drift, all in read-only mode.
      -
    • A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to read Microsoft 365 tenant data, such as users, license usage, and stale accounts, while enforcing least-privilege by refusing to run with excessive Azure permissions.
      4
      MIT

    TDQS

    C2.7/5.0

    Scored across 66 tools

    Disambiguation2/5

    Many tools overlap heavily: list_users and list_entra_users both list Entra users; the generic graph_* tools (graph_list, graph_get, graph_query, graph_relationship) duplicate specific list_*/get_* tools; and multiple assessment/NL-query tools (run_iam_assessment, run_enterprise_identity_audit, graph_assessment, iam_natural_language_query, graph_answer_identity_question) have unclear boundaries. An agent would struggle to pick the right tool without opening descriptions.

    Naming Consistency4/5

    Nearly all tool names use lower snake_case with a verb_noun pattern (list_users, get_role_risk_score, run_iam_assessment, graph_list), so the set is predictable overall. Minor deviations like identity_360, graph_directory_objects, and the *_natural_language_query suffix are readable but break the strict verb_noun convention.

    Tool Count1/5

    66 tools is extreme for an MCP server and far exceeds the 15-tool guideline. The surface contains many redundant wrappers and overlapping assessment/query tools, so the count is not justified by distinct capabilities.

    Completeness4/5

    For a read-only Azure identity and security assessment server, the surface is broad: it covers users, RBAC, PIM, MFA, applications, agents, licenses, resources, and ownership. Minor gaps exist around remediation or write operations, but those may be intentionally out of scope.

    Maintenance

    ActivityNo data
    ResponsivenessNo issues