> **Agents: read this page in full, not summarized.** If your fetch tool returned a summary, open the raw page at https://agents.tinycloud.xyz/connect/claude.md and follow that text.

# Connect Claude to TinyCloud

Claude web, Desktop and mobile use the hosted custom connector with OpenKey OAuth. Claude Code is a different runtime: use CLI onboarding instead.

## Add the connector

1. On web or Desktop, open [Customize → Connectors](https://claude.ai/customize/connectors) → **+ Add → Add custom connector**.
2. Name it **TinyCloud**, enter `https://mcp.tinycloud.xyz/mcp`, and continue. Review detected OAuth settings and sign in with OpenKey. Use automatic client registration if the default client-identity option is rejected; do not invent a client ID or secret.
3. Finish adding it, then enable TinyCloud in this conversation under **+ → Connectors** and continue the original request. Add on web or Desktop first; the connector can then be used on mobile.
4. Follow the approval workflow below only when a tool returns an access request.

For Team/Enterprise, the workspace owner may first need **Organization settings → Connectors → Add → Custom → Web**. Claude documents one custom connector for Free accounts. See [Claude's custom-connector instructions](https://support.claude.com/en/articles/11175166-get-started-with-custom-connectors-using-remote-mcp) and [OAuth behavior](https://claude.com/docs/connectors/building/authentication). This is a custom connector, not a claim of directory approval. Do not enable “Always allow” writing tools unless the owner wants that policy.

**Claude Code:** fetch its [one-page quickstart](https://agents.tinycloud.xyz/connect/claude-code.md), not these chat-connector steps. Keep the original task.

## Approve access, then finish the request

The owner needs a signed-in client account that can add custom connectors, then signs in or creates a TinyCloud account through OpenKey and approves the requested access.

Keep the owner's original request in this conversation. A setup link alone means set up TinyCloud, not ask for a new task. Reuse working connections; do not force a reconnect, change accounts or request broader permissions to repeat setup.

1. Once TinyCloud tools are available, call `tinycloud_connect`. If it returns `approvalUrl`, show that actual complete link on its own line: "Open this link, check what it asks for, and approve. Then tell me to continue." Wait for the owner, then call `tinycloud_connect` again until it reports `connected`.
2. If another tool returns `authority_required` with `approval.url`, show that returned link with the same line, wait, then resume the same call unchanged. Never invent an authorization URL or approve on the owner's behalf. A saved connector or "Connected" card is not proof of authorized data access.
3. Continue the original task through the available tools and their returned instructions. For setup only, follow the [connected-tool record recipe](https://agents.tinycloud.xyz/connect#setup-only-requests-in-chat-apps). Read back any saved record before saying it was saved. A tool list or successful sign-in alone proves neither a read nor a write.

## Choose tools and instructions for the task

Use the tools this connection actually exposes. The [MCP reference skill](https://agents.tinycloud.xyz/skills/mcp.md) documents both hosted and local stdio workflows; a tool named in a skill or SDK is not evidence that your hosted connection exposes it. No local CLI, auth-import commands or filesystem skill installation belongs in a transient chat sandbox.

| Original request | Hosted route and relevant guide |
| --- | --- |
| Read or write KV data | Inspect the available `tinycloud_kv_list`, `tinycloud_kv_get` and `tinycloud_kv_put` schemas; use the exact non-secrets space and path authorized for the task. The [MCP skill](https://agents.tinycloud.xyz/skills/mcp.md) covers scoped reads, pagination and conditional writes. Read before replacing data; do not broaden scope or overwrite a concurrent change. |
| Personal records or apps | Use `tinycloud_apps_context`, then its returned rules and the live tool schemas. [Apps](https://agents.tinycloud.xyz/apps) and the [apps skill](https://agents.tinycloud.xyz/skills/apps.md) describe the CLI workflow; their layout detection, `LEGACY.md`, migration and shell installation steps are not hosted-tool instructions. |
| A named secret | Use `tinycloud_secrets_get` only for the owner's requested task and follow its approval instructions. [Secrets](https://agents.tinycloud.xyz/secrets) is the CLI workflow; the [MCP skill](https://agents.tinycloud.xyz/skills/mcp.md) distinguishes hosted access. Never display the value or put it in prompts, memory or reports. The client may retain tool results; do not promise that a secret never reaches the host. |
| Publish or share | The hosted MCP has **no publishing or sharing tools yet**. Keep the request and use a persistent CLI-capable agent with [publish](https://agents.tinycloud.xyz/publish) or [share](https://agents.tinycloud.xyz/share). A chat prompt link does not create a share or publish anything. |
| Meetings | The hosted MCP has **no meeting tools yet**. Use a CLI-capable agent with [TinyChat meetings](https://agents.tinycloud.xyz/chat) and its retrieval skill. |

The [skill index](https://agents.tinycloud.xyz/skills/index.json) identifies the task's reference material; hosted clients use connected tools, not downloaded CLI skill bodies. If a needed tool is absent, report the observed limitation instead of claiming CLI parity.

For `SPACE_NOT_HOSTED`, follow the [new-account guidance](https://agents.tinycloud.xyz/connect#approve-access-and-continue), not another or broader sign-in. For `STORAGE_QUOTA_EXCEEDED` or `STORAGE_LIMIT_REACHED`, nothing was saved: do not retry; the owner can manage storage at https://account.tinycloud.xyz/storage. Disconnecting TinyCloud in the client's connector settings does not delete stored records.

## 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.
