Connect OpenClaw to TinyCloud
Use TinyCloud CLI in the OpenClaw execution environment when it has a persistent shell. The chat channel does not determine where tools or credentials run.
Preferred CLI route
Read and follow https://agents.tinycloud.xyz/connect for the current client in the active workspace/node, preserving the owner's request. Run the CLI on that host.
Native remote MCP alternative
If the CLI cannot run but the Gateway's native OAuth MCP is available, configure it on the Gateway, preserving existing servers:
openclaw mcp set tinycloud '{"url":"https://mcp.tinycloud.xyz/mcp","transport":"streamable-http","auth":"oauth","oauth":{"scope":"tinycloud:mcp offline_access"}}'
openclaw mcp login tinycloud
Send only the actual login link returned by that command; the owner signs in with OpenKey. Check openclaw mcp status --verbose and openclaw mcp doctor tinycloud --probe, then use the hosted approval workflow and MCP skill. Probes alone do not verify a record read or write. OpenClaw's transport reference documents this OAuth route. Node-hosted MCP is different and does not run Gateway-managed OAuth; do not work around that by asking for a token in chat.
The native OAuth configuration above is shared, operator-managed access by default. Use it only in the intended owner's trust boundary; do not present it as isolated per-user access on a shared Gateway. Per-requester OAuth requires gateway.publicOrigin and a separate identity flow documented by OpenClaw. Setting a registry entry or reading status does not open an MCP session; doctor --probe performs the connection probe.
This is a custom configuration, not an official TinyCloud directory listing. Verify an authorized task operation before reporting success.
CLI route: continue with the right skill
Only for a runtime using the CLI route: keep the original request, owner, profile and host. Fetch onboarding raw and follow it in this conversation, including its actual OpenKey approval links. Do not copy an old sign-in URL, request credentials in chat, overwrite an existing profile or broaden permissions to make a check pass. Existing grants are reused; missing task-specific access follows the relevant guide. If you chose the remote MCP alternative above, follow its hosted workflow instead of the CLI route.
| Original request | Guide and skill |
|---|---|
| KV read/write or other data work | All abilities and the CLI skill. Inspect the selected CLI's command help; use the authorized space/key and read back writes before claiming success. |
| Personal records, context or a small app | Apps, with tc-apps (apps). |
| A named API key or other secret | Secrets, with tc-secrets (secrets). Use it for the requested operation without displaying or copying the value into chat, memory or reports. |
| Publish or share a document/page | Publish or share, with tc-publish (publish). Make the link only with the owner's permission. |
| Meeting recap, follow-ups or transcript search | TinyChat meetings, with tinychat-retrieval (chat). |
The hosted server at https://mcp.tinycloud.xyz/mcp is a separate remote OAuth surface. Unlike the CLI route, it has no publishing, sharing or meeting tools yet. A locally installed stdio MCP process is not that hosted connection; neither a vendor directory listing nor a prompt link establishes either one.
If something went wrong
Help the next agent avoid the same problem: report it using the agent reporting instructions. Ask the owner first, with a short summary of what happened and any attachments you'd send; send nothing without their OK, and never include personal data or secrets.