OpenClaw

MCP client mode

Current OpenClaw documentation distinguishes running OpenClaw as an MCP server from saving third-party servers for OpenClaw-managed runs. ComputerUse uses the latter: register the ComputerUse stdio command in the OpenClaw MCP settings for the selected agent runtime.

The command is python -m computeruse.mcp from the source environment. Inject COMPUTERUSE_API_ORIGIN and COMPUTERUSE_API_TOKEN securely. Start with account:read; purchase and assignment tools require additional authorization.

Verify the connection

Use the installed release's openclaw mcp status --verbose, then its probe command to connect and list tools. Confirm the expected management tool names. Runtime eligibility and tool filters matter; saving a server does not prove that every OpenClaw runtime can use it.

Hosted OpenClaw

Running the agent within a customer guest is a separate offering. Its state and messaging-channel credentials persist on disk. Keep the gateway private and prefer outbound messaging connections. Do not expose an unauthenticated gateway to the Internet.

Scope of support

The rental-management bridge is implemented. Live ComputerUse screen control, installed-client validation and a ready-made OpenClaw guest template are pending. This guide does not claim they are already deployed.

Official reference: OpenClaw MCP documentation.