gobuster-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| KALI_HOST | No | SSH hostname or alias for the Kali Linux host | kali |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| gobuster_dirA | Directory/file enumeration mode - discovers hidden directories and files on web servers using wordlist-based brute forcing. Executes on remote Kali host via SSH. |
| gobuster_dnsA | DNS subdomain enumeration mode - discovers subdomains for a target domain using wordlist-based brute forcing. Executes on remote Kali host via SSH. |
| gobuster_vhostB | Virtual host enumeration mode - discovers virtual hosts on a web server by brute forcing Host header values. Executes on remote Kali host via SSH. |
| gobuster_fuzzA | Fuzzing mode - replaces the FUZZ keyword in URLs, headers, or POST data with wordlist entries. Useful for parameter discovery and testing. Executes on remote Kali host via SSH. |
| gobuster_s3A | Amazon S3 bucket enumeration mode - discovers open S3 buckets using wordlist-based brute forcing. Executes on remote Kali host via SSH. |
| gobuster_tftpB | TFTP file enumeration mode - discovers files on TFTP servers. Executes on remote Kali host via SSH. |
| gobuster_statusA | Check the status of an asynchronous gobuster scan |
| gobuster_stopA | Stop a running asynchronous gobuster scan |
| gobuster_list_scansA | List all active and recent gobuster scans |
| gobuster_wordlistsA | List available wordlists on the Kali host |
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 10 tools
Each tool maps to a distinct gobuster mode (dir, dns, vhost, fuzz, s3, tftp) or management function (status, stop, list scans, wordlists), so there is no overlap or ambiguity. Agents can easily select the right tool for the target.
All tools share the 'gobuster_' prefix, but the suffix mixes mode nouns (dir, dns, vhost) with action verbs (stop, list_scans). This is predictable and readable, but not a pure verb_noun pattern throughout.
With 10 tools, the server is well-scoped for a single-purpose gobuster interface. Each enumeration mode earns its place, and management/utility tools are minimal but sufficient.
The tool set covers all standard gobuster enumeration modes and the scan lifecycle (status, stop, list). A minor gap is the lack of an explicit 'get results' tool, but status likely returns findings, so agents can work around it.