> **Agents: read this file raw, not summarized.** If your fetch tool returned a summary, fetch it again with `curl -fsSL https://agents.tinycloud.xyz/connect/hermes.md` and follow that text. Summaries drop the shell blocks you must run.

# Connect Hermes to TinyCloud

Use TinyCloud CLI when Hermes has a persistent terminal backend that can run it. Keep the selected CLI and owner profile in that execution environment.

## Preferred CLI route

Read and follow https://agents.tinycloud.xyz/connect for the current client without asking the owner to repeat the task.

## Native remote MCP alternative

When the CLI cannot run but Hermes native HTTP OAuth is supported, merge the following into the active `~/.hermes/config.yaml`:

```yaml
mcp_servers:
  tinycloud:
    url: "https://mcp.tinycloud.xyz/mcp"
    auth: oauth
```

Run `hermes mcp login tinycloud`, present only its real returned link, and let the owner sign in with OpenKey. Use the [hosted approval workflow](https://agents.tinycloud.xyz/connect#approve-access-and-continue) and [MCP skill](https://agents.tinycloud.xyz/skills/mcp.md). [Hermes' MCP reference](https://hermes-agent.nousresearch.com/docs/user-guide/features/mcp) describes native OAuth, registration, refresh and credential storage. If native scope controls are exposed, request `tinycloud:mcp offline_access`; do not replace OAuth with a pasted bearer token. No optional gateway skill or local stdio server is required for the documented native route.

On a remote/headless host, the owner's browser cannot reach that host's loopback callback automatically. Use a supported Desktop relay, SSH forwarding or pasteback flow from [Hermes' remote OAuth guide](https://hermes-agent.nousresearch.com/docs/guides/oauth-over-ssh). Do not invent a device-code flow: it needs an advertised device authorization endpoint. If no supported callback route is available, report that blocker rather than claiming sign-in completed.

This is a custom configuration, not an official TinyCloud integration listing. Verify an authorized tool operation before reporting data access.

## 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](https://agents.tinycloud.xyz/onboarding.md) 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](https://agents.tinycloud.xyz/setup) and the [CLI skill](https://agents.tinycloud.xyz/skills/cli.md). 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](https://agents.tinycloud.xyz/apps), with `tc-apps` (`apps`). |
| A named API key or other secret | [Secrets](https://agents.tinycloud.xyz/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](https://agents.tinycloud.xyz/publish) or [share](https://agents.tinycloud.xyz/share), with `tc-publish` (`publish`). Make the link only with the owner's permission. |
| Meeting recap, follow-ups or transcript search | [TinyChat meetings](https://agents.tinycloud.xyz/chat), 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](https://feedback.tinycloud.xyz) using the [agent reporting instructions](https://feedback.tinycloud.xyz/agents.md). 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.
