Main
Use the TUI for interactive triage, then switch to MCP server mode when you need to remote-control runs from another agent or workflow runner.
Keep engagements safe and auditable: define scope explicitly, run tools in Docker for repeatability, and persist notes/results for review.
Treat it like an ops pipeline: start with passive recon tasks, then expand only when you have written authorization and a clear stop condition.
Source-backed notes
- README shows a TUI launch via
pentestagentand a target flag (-t). - README documents MCP server mode over stdio and SSE transports via
pentestagent mcp_server .... - README includes Docker run examples for running tools in containerized environments.
FAQ
- Is it for authorized testing only?: Yes—only run it against systems you own or have explicit permission to test.
- Does it support MCP?: Yes. README documents
mcp_serverwith stdio and SSE transports. - Do I need Docker?: No, but Docker helps make tool runs reproducible across machines.