name: mcp-orchestration description: Use when orchestrating headless tooling via MCP in this container (filesystem, fetch, playwright, semgrep, trivy, promptfoo, sqlite, kubernetes). Ensures outputs are saved under /pentest/ and avoids brittle npx cold-starts. license: MIT metadata: owner: mayflowergmbh/kali-ai-redteam
MCP Orchestration (Headless)
Available MCP Servers (Configured By entrypoint.sh)
filesystem: read/write under/pentest,/tmp,/var/logfetch: HTTP client (mcp-server-fetch)playwright: headless browser automationmemory: scratch memory for the sessionpromptfoo: run evals/redteamtrivy: runtrivy mcpfor scanssemgrep: runsemgrep-mcpfor repo scanssqlite: local db at/pentest/mcp.sqlitekubernetes: cluster inspection (useskubectlconfig)
Conventions
- Always write artifacts to
/pentest/(never to$HOME). - Cache expensive results and summarize them into
/pentest/reports/. - If an MCP server is unavailable, fall back to the CLI tool directly.