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
Ask Muse to prepare an authenticated connection:3. Verify the connection
Start with this read-only request:4. Troubleshooting
- Muse suggests Muse Code settings: this guide is for Muse web; a CLI settings file will not configure this connection.
- Muse asks for the key in chat or code: stop and use protected credential entry. Do not expose the key to make a generated connector work.
- Connector was created but the read fails: inspect the tool error, exact endpoint and credential. If it is only describing a call, ask for the actual read-only tool result.