Skip to main content
Glama
johanrobbenites

Mythic MCP

by johanrobbenites
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
MYTHIC_HOSTYesThe hostname or IP address of the Mythic server.
MYTHIC_PORTYesThe port number of the Mythic server.
MYTHIC_PASSWORDYesThe Mythic admin password.
MYTHIC_USERNAMEYesThe Mythic admin username.

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
run_as_userC

Attempt to authenticate as another user (network calls only) for the current session.

Args:
    username: Username of network account to use
    password: Password of network account to use
execute_mimikatzC

Runs mimikatz with the provided arguments, returning the output.

read_fileA

Reads a file using the ReadFile win32 API call. Returns the contents of that file.

Args:
    agent_id: ID of agent to read file from
    file_path: Path to the file to read on the target server
run_shell_commandB

Execute a shell script command line against a running agent. This script is executed using the default command line interpreter.

Args:
    agent_id: ID of agent to execute command on
    command_line: A command to be executed
get_all_agentsA

Returns a list of active agents

privilege_escalation_peasB
Run linPEAS or winPEAS on the target agent for privilege escalation discovery.

Args:
    agent_id: Mythic agent ID
    os_type: 'linux' or 'windows'
    peas_base64: Base64 encoded linpeas.sh or winPEAS.exe
    mode: 'quiet' or 'full'
run_sharphoundA
Run SharpHound (BloodHound collector) on a Windows agent.
SharpHound.exe must already exist on the target system.

Args:
    agent_id: ID of the Mythic agent
    collection: SharpHound collection methods (Default: All)
    output_dir: Directory to store SharpHound output ZIP
    stealth: Use stealth collection (recommended)
execute_powershellB

Execute a PowerShell script on the target agent. The script is sent raw and encoded to UTF-16LE for -EncodedCommand.

ad_reconC

Run AD reconnaissance commands and collate results.

enum_domain_usersB

Attempt to enumerate domain users. Uses AD cmdlets if available, falls back to net user /domain.

run_kerberoastB

Upload and run Rubeus (Kerberoasting).

upload_fileA

Upload a file to the Mythic server, and then upload the file to the remote target

Args:
    agent_id: ID of the agent to execute command on
    file_name: Name to give the file when uploading to Mythic server
    remote_path: Full path to where the file will be uploaded
    content: Base64 encoded contents of the file

Prompts

Interactive templates invoked by user choice

NameDescription
start_pentest
start_recon

Resources

Contextual data attached and managed by the client

NameDescription

No resources

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

B3.2/5.0

Scored across 12 tools

Disambiguation4/5

Most tools target distinct actions (file read vs. upload, shell vs. PowerShell, mimikatz vs. Rubeus), but ad_recon and enum_domain_users overlap in purpose, as enum_domain_users is a specific subset of AD reconnaissance. This is a minor ambiguity rather than a major one.

Naming Consistency4/5

The majority follow a verb_noun pattern (read_file, run_shell_command, execute_powershell, upload_file), but ad_recon and privilege_escalation_peas deviate by using nouns or abbreviations without a clear verb. The inconsistency is noticeable but not chaotic.

Tool Count5/5

With 12 tools, the set is well-scoped for a post-exploitation/Mythic C2 server. Each tool serves a clear function in the red-team workflow, and the count fits comfortably within the ideal range without feeling bloated or sparse.

Completeness4/5

The set covers core post-exploitation activities: execution, file operations, credential theft, privilege escalation, and AD reconnaissance. Missing features like process listing or lateral movement are notable but not critical for the primary purpose, and agents can often work around these gaps.

Maintenance

ActivitySlowing
ResponsivenessNo issues

Resources