Set defaults for all other detected ports with otherPortsAttributes: {"otherPortsAttributes": {"onAutoForward": "silent"}}
Prefer forwardPorts over the legacy appPort property: appPort publishes the port via Docker at container level, is not app-aware, and requires the app to listen on 0.0.0.0 rather than localhost
portsAttributes keys are strings ("3000" or ranges like "40000-55000") while forwardPorts entries are numbers — a numeric key typo means the attributes silently don't apply
forwardPorts-style forwarding lets container apps listen on localhost; appPort-published ports are only reachable if the app binds 0.0.0.0
Auto-forward detection reacts to processes that start listening; ports opened before the tool connects may need an explicit forwardPorts entry to be guaranteed
onAutoForward: ignore stops auto-forwarding a detected port, but ports listed in forwardPorts are still forwarded
Give your agent this knowledge — and 17,300+ more routes
One MCP install gives any agent live access to the full route map across 5,900+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?