Kali Metasploit MCP Server
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_exploitsC | Search for exploits in Metasploit database |
| search_auxiliaryC | Search for auxiliary modules in Metasploit |
| get_exploit_infoC | Get detailed information about a specific exploit |
| get_payloadsC | List available payloads for a specific exploit |
| db_statusB | Check Metasploit database status |
| db_workspacesB | List all Metasploit workspaces |
| db_hostsB | List all hosts in the current workspace |
| db_servicesB | List all services in the current workspace |
| nmap_scanC | Run an nmap scan and import results into Metasploit database |
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 9 tools
Each tool has a clearly distinct purpose targeting specific Metasploit functions: database queries (db_hosts, db_services, db_status, db_workspaces), module information retrieval (get_exploit_info, get_payloads), scanning (nmap_scan), and searching (search_auxiliary, search_exploits). No overlap exists that would cause confusion.
The naming shows mixed conventions: db_* tools follow a consistent pattern, but others use different styles like get_*, nmap_*, and search_*. While readable, the lack of a unified pattern across all tools reduces consistency.
With 9 tools, the count is well-scoped for a Metasploit server, covering core database management, scanning, and module exploration. Each tool earns its place without feeling excessive or insufficient.
The toolset provides strong coverage for Metasploit's key workflows: database status/query, scanning, and module search/info. Minor gaps exist, such as lacking tools for executing exploits or managing sessions, but agents can still perform essential reconnaissance and planning tasks.