Ligolo-ng MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| KALI_HOST | No | SSH hostname or alias for your Kali machine | kali |
| LIGOLO_API_PORT | No | Port for the Ligolo-ng web API | 8080 |
| LIGOLO_INTERFACE | No | Default TUN interface name | ligolo |
| LIGOLO_PROXY_PORT | No | Port for agent connections | 11601 |
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 |
|---|---|
| ligolo_proxy_startB | Start the ligolo-ng proxy server on Kali. The proxy accepts agent connections and manages tunnels. |
| ligolo_proxy_stopA | Stop the running ligolo-ng proxy server on Kali |
| ligolo_proxy_statusA | Check the status of the ligolo-ng proxy server |
| ligolo_agents_listA | List all connected agents to the ligolo-ng proxy |
| ligolo_session_selectB | Select an agent session to work with |
| ligolo_interface_createB | Create a TUN interface for ligolo-ng tunneling |
| ligolo_interface_listA | List all TUN interfaces on Kali |
| ligolo_tunnel_startB | Start a tunnel through a selected agent session |
| ligolo_tunnel_stopA | Stop the active tunnel |
| ligolo_route_addB | Add a route to access the agent's network through the tunnel |
| ligolo_route_deleteB | Delete a route from the routing table |
| ligolo_route_listA | List all routes configured for ligolo interfaces |
| ligolo_listener_addA | Add a listener on the agent to forward ports back to the attacker |
| ligolo_listener_listA | List all active listeners |
| ligolo_listener_deleteC | Delete a listener |
| ligolo_agent_infoA | Get network information from the selected agent (ifconfig) |
| ligolo_certificate_fingerprintA | Get the certificate fingerprint for agent verification |
| ligolo_agent_commandC | Generate the agent command to run on target machines |
| ligolo_send_commandB | Send a raw command to the ligolo-ng proxy console (advanced) |
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 19 tools
Tools cover distinct functional areas: agent management, proxy control, routing, tunneling, interface, and listeners. While there is slight overlap between session selection and agent info, descriptions likely clarify. Overall, each tool has a clear purpose.
All tools share the 'ligolo_' prefix and snake_case, but the pattern varies: most are noun_verb (e.g., ligolo_agents_list, ligolo_route_add), while some are noun_noun (e.g., ligolo_certificate_fingerprint) and one is verb_noun (ligolo_send_command). This inconsistency could confuse an agent.
19 tools cover the primary operations of ligolo-ng (agent, proxy, routing, tunneling, listeners, interface). This is a reasonable count; not too sparse or overwhelming for the intended domain.
The set includes CRUD-like operations for key elements (routes, listeners, interfaces) and essential proxy/agent controls. Minor gaps like agent disconnection or route modification are addressable via the send_command tool, so coverage is solid.