Configuration Reference

The plugin owns OpenClaw-specific logic while delegating protocol handling to @aiwerk/mcp-bridge.

Translation mapping

• transports[0].type -> transport
• transports[0].command -> command
• transports[0].args -> args
• transports[0].env -> env
• metadata.tags -> keywords
• metadata.category -> prepended to keywords (deduplicated)

Env resolution chain

Priority high -> low:

1. OpenClaw config env.vars
2. Shell environment
3. ~/.openclaw/.env
4. pass values injected by generate-env.sh

The plugin does a second-pass resolution for unresolved ${...} placeholders and warns if still missing.

Modes

• Direct mode: register each tool via registerTool
• Router mode: register one mcp tool
• Smart filter (router extension): semantic narrowing using keywords + descriptions

Lifecycle summary

• Startup: activate plugin and connect/register based on mode
• Reconnection: unregister stale tools, reconnect after interval, re-register
• Shutdown: disconnect all servers and cleanup child processes

See adapter spec sections 2-7 and Modes.