Skip to main content
Glama
schwarztim

CrackMapExec MCP Server

by schwarztim

cme_ldap

Execute LDAP enumeration and custom queries against Active Directory domain controllers to discover users, computers, groups, and delegation settings.

Instructions

Execute LDAP protocol operations. Supports Active Directory enumeration including users, computers, groups, delegation, and custom LDAP queries.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
targetsYesTarget Domain Controller IP or hostname
usernameNoUsername or file path to usernames
passwordNoPassword or file path to passwords
hashNoNTLM hash for pass-the-hash
domainNoDomain name
kerberosAuthNoUse Kerberos authentication
portNoLDAP port (default: 389, 636 for LDAPS)
threadsNoConcurrent threads
usersEnabledNoEnumerate enabled users
computersNoEnumerate computers
dcNoEnumerate domain controllers
trustedForDelegationNoFind accounts trusted for delegation
passwordNotReqdNoFind accounts with PASSWD_NOTREQD flag
adminCountNoFind accounts with adminCount=1
gmsaNoDump gMSA passwords
ldapQueryNoCustom LDAP query
moduleNoModule to run
moduleOptionsNoModule options
verboseNoVerbose output
debugNoDebug output
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description must cover behavioral traits. It mentions enumeration but does not clarify whether write operations are supported, authentication requirements, error handling, or potential side effects. This is insufficient for a tool with 20 parameters.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise with two sentences that front-load the core purpose and follow with examples. No unnecessary words, but could be slightly more structured with bullet points.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 20 parameters and no output schema or annotations, the description is incomplete. It does not explain return values, error handling, authentication requirements, or how to use the custom LDAP query parameter. For a complex tool, more detail is needed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3. The description does not add meaning beyond what the schema already provides; it only repeats examples of what can be enumerated, which maps to parameters but adds no new detail.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool executes LDAP protocol operations and enumerates Active Directory objects, listing specific examples like users, computers, groups, delegation, and custom queries. This distinguishes it from sibling tools that target other protocols.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for LDAP enumeration but does not explicitly state when to use this tool versus alternatives like cme_smb or cme_mssql. No when-not-to-use or exclusion criteria are provided.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/schwarztim/sec-crackmapexec-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server