Connect Grok to TinyCloud
Grok chat uses a custom hosted MCP connector with OpenKey OAuth. Grok Bot can instead use the CLI when its actual runtime can run it.
Grok chat
- Open grok.com/connectors → New Connector → Custom.
- Enter
https://mcp.tinycloud.xyz/mcpand complete the native OAuth sign-in with OpenKey. - Continue the original request in a conversation; Grok discovers the connector's tools. Follow any actual TinyCloud access link as described below.
On Grok Business/Enterprise, a team admin must provision the connector first. xAI's connector reference distinguishes built-in, catalog and custom connectors. This guide configures a custom one; it does not establish a TinyCloud catalog listing.
Grok Bot is runtime-dependent
If Grok Bot has a persistent terminal that can run the CLI, fetch its one-page quickstart. Otherwise use its native MCP-by-URL setup with https://mcp.tinycloud.xyz/mcp only if OAuth is available. If neither route is supported, state that limitation; do not ask for a token in chat. See xAI's computer and apps reference.
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.
- Once TinyCloud tools are available, call
tinycloud_connect. If it returnsapprovalUrl, 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 calltinycloud_connectagain until it reportsconnected. - If another tool returns
authority_requiredwithapproval.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. - 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.