Skip to main content
Use Nous Research’s Hermes Agent as an MCP client for Plainrouter. Start with an installed Hermes environment and a configured model provider. 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

Add a production server under mcp_servers in your private local config:
Replace the placeholder only in that private file; keep it out of repositories and shared config exports. Remove an old 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:
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

  • 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 plainrouter connection.
Reference: Hermes MCP configuration, reload and tool naming. Choose another client.