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
Add a production server undermcp_servers in your private local config:
plainrouter-test sandbox entry if present. Reload MCP or start a new session. The URL connects over HTTP; do not configure Plainrouter as a local command.
3. Verify the connection
Start with this read-only request:4. Troubleshooting
- New server is missing: reload the Hermes session or gateway that actually owns the connection.
- 401 on calls: check the complete bearer header and current key. A Server secret cannot authenticate MCP.
- Tool names differ: Hermes prefixes MCP tool names with the server name. Select tools belonging to the authenticated
plainrouterconnection.