kali-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| container_startA | Start the Kali Linux Docker container. Must be called before running any commands. |
| container_stopA | Stop and remove the Kali Linux Docker container. |
| container_statusB | Check the status of the Kali Linux Docker container. |
| execute_commandA | Execute a shell command inside the Kali Linux container. Use this to run security tools like nmap, sqlmap, hydra, nikto, gobuster, john, hashcat, dirb, enum4linux, and any other installed tool. |
| upload_fileA | Upload/write a file to the Kali Linux container. Useful for uploading wordlists, scripts, or configuration files. |
| download_fileA | Read/download a file from the Kali Linux container. Useful for retrieving scan results and output files. |
| list_filesB | List files in a directory inside the Kali Linux container. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Each tool has a unique purpose: container lifecycle management, file transfer, command execution, and file listing. No overlap or ambiguity.
All tool names follow a consistent verb_noun pattern in snake_case, making them predictable and easy to understand.
With 7 tools, the set is well-scoped for managing a Kali container and running tools. Slightly compact but sufficient for core workflows.
Covers container lifecycle, file transfer, file listing, and command execution. Minor gap: no tool for container logs or interactive session, but typical use cases are covered.