Connect Meta Muse to TinyCloud

Ask Muse to create a native custom connector to TinyCloud hosted MCP, then continue the same task. Do not install the CLI in a transient chat sandbox.

Native connector setup

For Muse: the owner's original setup link or task is sufficient. Do not ask for a second “create a connector” prompt, a repeated task or a choice of integration method. Do not stop at generated connector files.

  1. Reuse an existing TinyCloud connector if live tools work. Do not disconnect it just to repeat setup.
  2. If setup is needed, use Streamable HTTP, server URL and OAuth resource https://mcp.tinycloud.xyz/mcp, and scopes tinycloud:mcp offline_access on the first sign-in. Discover the authorization and registration endpoints from the server metadata. Keep the resource and both scopes in saved configuration and reconnect instructions; no owner-created client ID or secret is required.
  3. Use Muse's native OAuth flow. Show the actual Connect card or fresh link returned by its setup tool, then wait for the owner to sign in and approve. Never fabricate an auth URL. Resume this same task when completion is observable; if it is not observable, ask only whether approval is finished.
  4. Run MCP tools/list and tinycloud_connect; a remembered success or “Added” card is not proof. Then call tinycloud_apps_context and complete the original task. Read back a saved record before reporting success. A first successful call does not verify refresh.

Only after an observed authentication failure, follow the Muse recovery instructions; disconnect only TinyCloud and only with the owner's approval. Do not delete connector files, skills or personal records. OAuth credentials stay in Muse's secure credential flow, not source files or memory.

Meta's connector help explains custom connectors and notes Meta does not review them. This guide is not an official listing.

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. 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 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 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 and the apps skill 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 is the CLI workflow; the MCP skill 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 or 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 and its retrieval skill.

The skill index 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, 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 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.