awsome_kali_MCPServers

This MCP server is a Kali Linux–oriented containerized MCP implementation. It exposes a collection of security, reverse engineering, and automation tools built to run inside a Docker sandbox. The included features cover network scanning (Nmap variants), binary analysis (nm, objdump, strings), and network traffic analysis (Wireshark/tshark) as part of a cohesive MCP workflow. With the kali-docker server configured in your MCP client, you can call tools such as basic_scan for a quick network sweep, disassemble to inspect a target binary, and capture_live to begin real-time traffic collection. The design aims to streamline repetitive tasks by exposing common toolchains through the MCP interface, enabling automated or scripted workflows within a Kali-focused environment.

Prerequisites:

• Docker installed and running on your host machine
• An MCP client (e.g., Claude Desktop, cline, Goose, or RooCode) ready to load MCP configurations

Step-by-step installation:

1. Build the Docker image locally

   docker build -t kali-mcps:latest .
   

2. Verify the image was built

   docker images | grep kali-mcps
   

3. Create the MCP configuration for your client In your MCP client, add a server entry named kali-docker with the following payload:

   {
     "mcpServers": {
       "kali-docker": {
         "command": "docker",
         "args": ["run", "-i", "kali-mcps:latest"]
       }
     }
   }
   

4. Save the configuration and connect

   • Ensure Docker is allowed to run containers from your MCP client
   • Connect to the kali-docker server from the MCP client interface

5. Run and test a sample tool

   • From your MCP client, invoke a tool like basic_scan to perform a quick network assessment inside the Kali container
   • You can also run disassemble on a target file or capture_live to start traffic capture

Tip: If you need a persistent container, you can customize the docker run arguments (e.g., add --rm=false, mount volumes) when configuring the server in your MCP client.

Tips and considerations:

• The kali-docker server runs a Kali-based image via Docker; ensure your host system permits Docker-in-Docker interactions if you plan to mount volumes or access host resources.
• Useful defaults include interactive mode (-i) to keep the container alive for multiple commands; customize as needed for batch automation.
• Some tools (e.g., network analyzers or sandbox features) may require elevated permissions or additional capabilities in the Docker run command.
• If you enable a sandbox-like workflow, you can adjust memory and CPU constraints per your host capacity, and consider mapping necessary files into the container for analysis.
• When using MCP clients, you can call the available tools such as basic_scan, intensed_scan, disassemble, capture_live, and other listed features to compose automated tasks or exploratory sessions.