> **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/chatgpt.md and follow that text.

# Connect ChatGPT to TinyCloud

Use a custom remote MCP plugin in ChatGPT with OpenKey OAuth. This is not an official TinyCloud directory listing; pasting this guide does not install a plugin.

**For the assistant:** preserve the original request. If TinyCloud tools are already available, continue it rather than repeating setup. Otherwise reply with **only these four numbered steps, at most 120 words**: no introduction, images, feature menu, speculative plan or price caveats, or closing question.

1. In a browser, open [ChatGPT Plugins](https://chatgpt.com/plugins) → **+ → Add custom MCP server**.
2. Enter **Name:** TinyCloud; **Description:** Personal records in TinyCloud; **Server URL:** `https://mcp.tinycloud.xyz/mcp`; **Authentication:** OAuth.
3. Review the warning, choose **Create as a plugin**, sign in with OpenKey, and install it.
4. In a conversation, type **@**, select **TinyCloud**, and continue your original request. For setup only: **“What personal apps do I already have in TinyCloud?”**

[OpenAI's custom MCP instructions](https://help.openai.com/en/articles/12584461-connecting-custom-mcp-servers-in-chatgpt) describe web setup and workspace administration. Troubleshoot only a reported or observed blocker: do not infer failure from the account's plan label or TinyCloud's absence from the directory, recommend an upgrade speculatively, or reconnect a working plugin. If a write is rejected, report that action's actual error; do not claim it saved. OAuth credentials belong in ChatGPT's native flow, not custom headers or chat.

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