Mythic

A simple POC to expose Mythic as a MCP server

python

73

GitHub Stars

python

Language

6 months ago

First Indexed

2 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs

{
  "mcpServers": {
    "xpn-mythic_mcp": {
      "command": "/Users/xpn/.local/bin/uv",
      "args": [
        "--directory",
        "/full/path/to/mythic_mcp/",
        "run",
        "main.py",
        "mythic_admin",
        "mythic_admin_password",
        "localhost",
        "7443"
      ]
    }
  }
}

You have a Mythic MCP server you can run locally to let an MCP client automate tasks. This setup enables you to launch a local MCP endpoint that your client connects to, so you can issue automated pentest-style tasks and receive structured responses via the MCP protocol. It’s useful for testing, prototyping, or running scripted workflows against your own environment.

How to use

To use this MCP server with an MCP client, configure the client to point at the local server, then start the server and run your client prompts. You will typically provide the local endpoint, credentials, and the client will send tasks to the server which executes them and returns results.

How to install

Prerequisites you need to have before running this MCP server are:

uv runtime available on your system
Python 3 installed
An MCP client such as Claude Desktop to connect to the server Install or verify these prerequisites on your system first, then proceed to configure and start the MCP server.

# Example prerequisites check (adjust to your OS)
pip3 --version
python3 --version
uv --version

Additional sections

This server is configured to run as a local MCP endpoint using uv to execute a Python script. The client will connect to localhost on the specified port and authenticate using the provided credentials within the startup command.

Note the credentials used during startup are included in the startup arguments. Treat these as sensitive and protect them accordingly. If you need to adjust the credentials, update the startup command and restart the MCP server.