Skip to main content
Glama
josimarh

azure-mcp-pilot

by josimarh
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to azure-mcp-pilot

No user-submitted related servers found.

    Related Servers

    • Entra ID SecOps MCP Server

      Sultan-zd
      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

    • MCP Microsoft Graph Server

      tcpatter
      -
      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.
      -

    • mcp-azure-landing-zone

      jmartinezHNL
      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.
      -

    • entra-mcp

      taitson
      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
    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

    C2.9/5.0

    Scored across 66 tools

    Disambiguation2/5

    Several tools have unclear boundaries, such as list_entra_users vs list_users, list_azure_role_assignments vs graph_role_assignments, and the multiple natural-language query and assessment tools. An agent could easily choose the wrong tool for user-listing, role-assignment, or timeline questions. A few tools like identity_360 and detect_toxic_combinations are distinct, but the overall set is highly ambiguous.

    Naming Consistency3/5

    Most tools follow readable snake_case list_/get_/run_ naming, but the set mixes conventions with names like identity_360, graph_assessment, and noun-first NL query tools such as pim_natural_language_query and agent_natural_language_query. The graph_* prefix is inconsistently combined with verbs, making the pattern predictable only part of the time.

    Tool Count1/5

    66 tools is an extreme number for an identity security audit server, and many tools are near-duplicates or could be consolidated into parameterized operations. This far exceeds the 25+ threshold and creates a heavy, unwieldy tool surface.

    Completeness4/5

    The surface is quite comprehensive for read-only identity governance: it covers users, RBAC, PIM, MFA, licenses, agent identities, blast radius, object ownership, provenance, and Graph/API access. Since this is an audit-focused server, missing create/update/delete is acceptable; minor gaps exist around detailed sign-in/audit log exploration and remediation actions.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources