Transports and Runtime

pwno-mcp supports two main runtime modes.

Main MCP endpoint defaults to http://127.0.0.1:5500/mcp
Health endpoint defaults to http://127.0.0.1:5500/healthz
Local attach helper API defaults to http://127.0.0.1:5501/attach
Best when your client wants a url or you want the server process to stay alive outside the client

The client launches python -m pwnomcp --stdio or the equivalent Docker command
No HTTP endpoint is involved
Best when your client expects a local command and args
The attach sidecar is not started in stdio mode

CLI defaults

Flag	Default	Purpose
`--host`	`0.0.0.0`	main HTTP bind host
`--port`	`5500`	main HTTP port
`--attach-host`	`127.0.0.1`	attach API bind host
`--attach-port`	`5501`	attach API port
`--http-path`	`/mcp`	HTTP transport path
`--stdio`	disabled	switches runtime into stdio mode

python -m pwnomcp

/mcp is the main FastMCP transport path in HTTP mode
/healthz returns a simple JSON status payload for health checks
/attach is a helper API for process-attach workflows driven by the local Python helper or external automation

The attach API is separate from the main MCP transport. It exists to make some attach workflows simpler for local helper scripts and integrations.

choose HTTP for persistent local servers, remote clients, and easy health checks
choose stdio for clients that only support local process-based MCP servers
keep the Docker capability and security flags the same in both modes