Skip to main content
Connect an installed OpenClaw agent to Plainrouter over Streamable HTTP. Configure the installation or Gateway that runs your agent. You need a Plainrouter account and access to the intended workspace. The unauthenticated sandbox is retired; start with a Read key and verify the workspace result.

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, call list_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:
Provide the variable securely to the process running the Gateway or agent, not just a separate terminal. Keep the reference in config. Apply the config, then run openclaw mcp doctor plainrouter --probe.

3. Verify the connection

Start with this read-only request:
Check the tool result, not just the assistant’s summary: the workspace must be yours and the call must succeed. This workspace-only read works before connecting Meta. For account diagnostics, connect Meta and verify the selected account. Agent replies can vary. In Ask, changes wait for approval. Auto can run enabled agent action types without individual approval; Full can run admitted agent actions without individual approval. Policy blocks remain effective in every mode. A client’s tool confirmation is separate from Plainrouter’s execution controls.

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.
References: OpenClaw MCP setup, config location, and HTTP header interpolation. Choose another client.