Skip to main content
Glama
fredriksknese

mcp-activedirectory

by fredriksknese
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to mcp-activedirectory

No user-submitted related servers found.

    Related Servers

    • Enterprise Microsoft 365 MCP

      ManoAlee
      A
      license
      C
      quality
      A
      maintenance
      Connects LLMs and AI agents to enterprise Microsoft 365 environments, enabling administration across Exchange Online, Microsoft Graph, Entra ID, compliance, security, mailbox operations, and mail-flow diagnostics through 34 tools.
      34
      MIT

    • RedHatLDAP-MCP

      jlaska
      A
      license
      B
      quality
      D
      maintenance
      Provides read-only access to corporate LDAP directories, enabling AI assistants to search for people, navigate organizational hierarchies, and export contact information.
      12
      5
      MIT

    • Koppla

      ruudmens
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables managing Active Directory users, groups, and computers using natural language, with support for queries and updates.
      59
      MIT

    • adslayer

      poamslayer
      A
      license
      A
      quality
      A
      maintenance
      Lets an AI agent read and change on-premises Active Directory by writing short JavaScript scripts that run in a network-isolated sandbox against a chosen domain. Runs on Windows as the logged-on user, over Kerberos, with tools for executing scripts, searching the domain's schema catalogue, querying Microsoft Learn docs, and managing domain connections and Group Policy objects.
      6
      24 npm
      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

    A3.5/5.0

    Scored across 18 tools

    Disambiguation5/5

    Each tool targets a distinct resource type or operation (e.g., get vs list vs search, computer vs device, group vs group members). There is no ambiguity between tools.

    Naming Consistency5/5

    All tool names follow the verb_noun pattern consistently (e.g., get_computer, list_users, search_groups). No mixing of naming conventions.

    Tool Count5/5

    18 tools cover both on-prem AD and Azure AD resources (users, groups, computers, devices, OUs, service principals) without being excessive. The scope is appropriate for a directory server.

    Completeness2/5

    The tool set is entirely read-only; there are no create, update, or delete operations. For an Active Directory server, this is a significant gap that prevents full lifecycle management.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources