Kali Linux

my first kali MCP made with claude
  • python

0

GitHub Stars

python

Language

7 months ago

First Indexed

3 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": {
    "pellax-kalimcp": {
      "command": "python3",
      "args": [
        "/home/pellax/Documents/myfirstclaudecode/kali_mcp_wrapper.py"
      ],
      "env": {
        "MCP_HOST": "127.0.0.1",
        "MCP_PORT": "8000",
        "MCP_OUTPUT_LIMIT": "10000",
        "WPSCAN_API_TOKEN": "YOUR_TOKEN",
        "MCP_MAX_EXEC_TIME": "300",
        "MCP_ALLOWED_NETWORKS": "192.168.0.0/16,10.0.0.0/8"
      }
    }
  }
}

You can run a Dockerized MCP Server that exposes Kali Linux security tools through a secure, controlled interface. This server is designed for defensive security work and authorized testing, offering a compact set of tools, input validation, network restrictions, and safe execution limits.

How to use

Start the containerized MCP Server and connect your MCP client (such as Claude Desktop) to run tools. The server uses a STDIO transport, so you interact through the wrapper script that bridges the client to the running container.

Typical workflow options include starting the server, then selecting and running tools such as network scanning, web application testing, and credential testing. You can perform actions like discovering hosts, enumerating services, scanning WordPress sites, testing for SQL injection, and cracking credentials, all while the server enforces input sanitization, execution timeouts, and output size limits.

How to install

# Prerequisites
# - Docker and Docker Compose installed
# - Sufficient disk space for the Kali Linux image

# 1) Create project directory and navigate into it
mkdir kali_mcp_project
cd kali_mcp_project

# 2) Prepare container configuration (docker-compose.yml and related files should be present in this directory)
# The container will start the MCP server automatically when you bring up the services

# 3) Build and start the container (MCP server starts automatically)
docker compose up --build

# Optional: run in background
# docker compose up -d --build

# 4) Verify the MCP server is running
docker compose ps

Configuration and usage notes

The server exposes several environment variables to control behavior and security. Set them to tailor the server to your environment before starting the container.

# Example: restrict scanning targets to internal networks
MCP_ALLOWED_NETWORKS=192.168.0.0/16,10.0.0.0/8,172.16.0.0/12

# Controls the maximum time a command can run (in seconds)
MCP_MAX_EXEC_TIME=300

# Limits the size of the tool output in bytes
MCP_OUTPUT_LIMIT=10000

# Server host and port
MCP_HOST=127.0.0.1
MCP_PORT=8000
```} ,{

Examples of usage inside the container

If you need to test tools directly inside the container, you can open a shell and run the installed tools to verify versions and paths.

# Access the container shell for debugging
docker compose exec kali_mcp_container bash

# Inside container, check tool versions
nmap --version
gobuster version
wpscan --version

Claude Desktop integration

Claude Desktop connects to the MCP Server via STDIO transport. A wrapper script handles the container communication and error reporting, enabling tool execution from the Claude UI.

To use this setup, start the container in the background and ensure the wrapper is configured in Claude Desktop as shown.

Tool usage overview

The MCP server provides a curated set of tools for network, web, system, and credential testing. Each tool is invoked through the client interface and is subject to input validation and safety limits.

Security considerations

Operate only in authorized contexts. Restrict access to the MCP server using network controls, audit logs, and proper authentication. Run the container as a dedicated non-root user with limited filesystem access and implemented timeouts.

Troubleshooting and notes

If the container fails to start or the MCP server does not respond, check container logs and verify that the required environment variables are set correctly. Use the real-time logs to diagnose startup issues and verify the wrapper is correctly bridging STDIO to Claude Desktop.

Notes on container management

Manage the container lifecycle with standard Docker Compose commands. Stop, restart, and rebuild as needed when you modify server code or configuration.

Available tools

nmap_scan

Network discovery and port scanning tool used to identify live hosts and open ports.

gobuster_dir

Directory and file enumeration tool to discover hidden resources on web servers.

wpscan_scan

WordPress security scanner to identify vulnerabilities and misconfigurations in WordPress sites.

sqlmap_test

SQL injection testing tool to assess parameterized queries and potential injections.

dirb_scan

Web content discovery tool to map out accessible web content.

enum4linux_scan

SMB/NetBIOS enumeration to gather information about Windows shares and services.

searchsploit_query

Query the Exploit Database for known vulnerabilities related to targets.

crackmapexec_smb

SMB credential testing and assessment tool.

john_crack

Password cracking with John the Ripper for weak credentials.

hashcat_crack

GPU-accelerated password cracking for intensive workloads.

netcat_connect

Network connectivity testing utility to verify reachability and ports.

bloodhound_py

Active Directory enumeration and visualization helper.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational