AGENTS & SDKS
Hermes Agent
Use Hermes with ComputerUse through its MCP client.
Configure a stdio server
Hermes uses mcp_servers in its configuration. The following shape launches the source-installed bridge; configure the two ComputerUse environment variables securely in the process environment rather than committing secret values:
mcp_servers:
computeruse:
command: python
args: ["-m", "computeruse.mcp"]
enabled: true
supports_parallel_tool_calls: false
The Python environment must be able to import the ComputerUse package. The API origin must point to an actual management service; the static marketing website is not an API server.
First verification
List the exposed tools and make a read-only stock/account call. Confirm that the returned rentals belong to the expected account. Only then enable write tools for an agent authorized to spend or assign resources. A management tool listing does not verify desktop control.
Persistent Hermes state
A hosted Hermes setup can retain learned skills, conversation state and credentials in its own data directory. Include those files and any external memory providers in the customer's retention controls. Ending a chat does not automatically erase them.
Scope of support
The bridge and this configuration target are available in source. A deployed Hermes client and actual desktop-controller workflow have not yet passed end-to-end verification.
Official reference: Hermes MCP configuration.