1. Create a workspace key
In Plainrouter, select your workspace and open Settings → Workspace keys. Create a Read key for analysis; use Write for Actions previews and proposals. A new Read key can also inspect Actions records and policy. Copy it once into your protected credential configuration. Select the intended workspace under Workspaces. A key can cover a fixed set of workspaces; for more than one, calllist_workspaces and pass workspace_id on later tool calls. Workspace selection. Never put keys in prompts or source control. Key permissions and replacement.
2. Add Plainrouter to the client
Merge this entry into~/.openclaw/openclaw.json, preserving existing settings:
openclaw mcp doctor plainrouter --probe.
3. Verify the connection
Start with this read-only request:4. Troubleshooting
- Config saved but no tools: run the probe and inspect tool policy or session restrictions; saving an entry alone does not establish a connection.
- 401 from a Gateway: check the credential environment on the Gateway host.
- Old configuration persists: reload or restart the process that owns the connection. A CLI reload does not reload a separate Gateway.