Skip to main content
Glama
schwarztim

CrackMapExec MCP Server

by schwarztim

cme_smb

Enumerate SMB shares, users, groups, and sessions; dump SAM, LSA, and NTDS credentials; execute commands via SMB with pass-the-hash and Kerberos support.

Instructions

Execute SMB protocol operations with NetExec/CrackMapExec. Supports enumeration of shares, users, groups, sessions, credential dumping (SAM, LSA, NTDS), and command execution.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
targetsYesTarget IP, hostname, CIDR range, or file path
usernameNoUsername or file path to usernames
passwordNoPassword or file path to passwords
hashNoNTLM hash for pass-the-hash
domainNoDomain name
localAuthNoUse local authentication
kerberosAuthNoUse Kerberos authentication
portNoSMB port (default: 445)
threadsNoConcurrent threads
sharesNoEnumerate shares
usersNoEnumerate domain users
groupsNoEnumerate domain groups
loggedOnUsersNoEnumerate logged on users
sessionsNoEnumerate active sessions
disksNoEnumerate disks
passPolicyNoDump password policy
ridNoRID brute force enumeration
samNoDump SAM hashes
lsaNoDump LSA secrets
ntdsNoDump NTDS.dit hashes (requires DC)
execCmdNoExecute cmd command
execPowershellNoExecute PowerShell command
execMethodNoExecution method: wmiexec, smbexec, atexec, mmcexec
moduleNoModule to run
moduleOptionsNoModule options (KEY=VALUE format)
verboseNoVerbose output
debugNoDebug output
Behavior2/5

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

No annotations are present, so the description carries full burden. It fails to disclose critical behavioral traits such as destructive potential (credential dumping, command execution), authentication requirements, or network impact, leaving the agent without safety or context information.

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

Conciseness5/5

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

Two concise sentences that efficiently convey the core purpose and supported operations without redundant or vague language.

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 27 parameters, no output schema, and no annotations, the description is too simplistic. It does not explain how to combine parameters, expected output format, or prerequisites (e.g., necessary permissions), leaving significant gaps for a tool of this complexity.

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 baseline is 3. The description adds some context by grouping operations into categories (enumeration, dumping, exec) but does not significantly enhance understanding of individual parameters beyond the schema.

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?

Description clearly states 'Execute SMB protocol operations' and lists specific capabilities (enumeration, credential dumping, command execution), distinguishing it from sibling tools like cme_ldap or cme_ssh.

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 SMB operations via NetExec, but does not provide when-to-use or when-not-to-use guidance, nor does it compare to alternatives among sibling tools.

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