Documentation version: 2026-10-02.6 Canonical: https://docs.creator.gg/guides/cloud-agents.md # Connect cloud agents and work across agents Creators' hosted tools work independently of local skill installation, shell access and browser control. Add a connection from https://agents.creator.gg/setup. Local agents can still use the versioned agent kit. A saved server URL is configuration, not proof that authorization or tool access succeeded. ## Connect a cloud host 1. In the host's connector controls, add Creators at https://mcp.creator.gg/mcp using remote Streamable HTTP and OAuth. Reuse a matching connector in this host and account; leave other agents' connections working. 2. Complete the host's sign-in flow yourself with your existing Creators account. Agents must not request passwords, tokens or cookies in chat, copy another agent's credentials, or automate account consent. 3. Enable the connector for the intended agent/conversation. Refresh its tools or start a new conversation if the host requires it. 4. Call workspace_status and confirm the returned workspace. Read documentation_get with id guides/start and guides/cloud-agents; follow nextLine when present. Read intelligence_get and growth_context_get when available. Report configuration, authorization and successful tool access separately. Setup does not authorize marketing actions or automation. The host must support a public OAuth client with PKCE S256, resource indicators, and either Client ID Metadata Documents or dynamic client registration. Discovery is served from the MCP endpoint's protected-resource metadata and https://agents.creator.gg/.well-known/oauth-authorization-server. Scope: creators:workspace; offline_access allows refresh when supported. Token endpoint authentication is none; no client secret is issued. A host requiring client_secret_basic or client_secret_post is not currently compatible. Do not invent a secret, proxy or REST adapter to make setup appear complete. Server-to-server requests do not need a browser Origin header. Browser requests remain subject to the configured origin policy. Do not bypass that policy or add broad wildcard access to onboard a host. ## Host routes and acceptance - ChatGPT / dots: add a custom MCP plugin with OAuth through ChatGPT's supported controls and enable it for the dot or conversation. Availability depends on plan, workspace policy and rollout. See https://learn.chatgpt.com/docs/extend/mcp and https://learn.chatgpt.com/docs/dots/computers-and-apps. Creators sign-in and tool use in dots still require host acceptance testing; this is not a marketplace listing. - Claude: add a custom connector for the server URL and complete Connect. Remote OAuth and workspace_status have been verified in Claude Desktop Chat. That evidence does not establish every Claude surface or plan. Setup link: https://claude.ai/customize/connectors?modal=add-custom-connector&connectorName=Creators&connectorUrl=https%3A%2F%2Fmcp.creator.gg%2Fmcp. - Grok Bot: add a custom MCP server with Remote HTTPS and OAuth through the Bot's plugin controls. Use each person's sign-in for a Team Bot rather than a shared credential. See https://docs.x.ai/grok-bot/team-bots. The route is documented by the host; Creators sign-in and tool use there still need acceptance testing. Grok Build is a different local client. - Muse: custom connectors are documented at https://www.meta.com/help/artificial-intelligence/1687253048996149/. This does not establish support for Creators' MCP transport and public OAuth flow. Compatibility is pending; do not claim a verified integration or substitute a shared account credential. - Other hosts: verify the transport, authentication and account policy above. Tool compatibility and browser capability are separate checks. ## Several agents, one business Use an independent OAuth authorization for each host/account. Adding one does not replace the others. The portal lists connections individually, including last use, and can revoke one without disconnecting the others. Each connection remains bound to its authorized person and workspace; a different account may select a different workspace. Verify workspace_status after connecting or switching context. Business intelligence and a linked saved growth plan belong to the workspace, not an agent's private memory. At the start of each task, read intelligence_get and growth_context_get. Reuse completed work, dependencies and recorded evidence. Local files, pasted briefs and model memories may be stale. Keep private context out of public templates and shared bot instructions unless the user specifically authorizes that audience. Before updating intelligence, read the current revision. Supply only intended changes with a new requestId. A revision conflict means another writer changed the record: re-read, reconcile and submit a new operation. Never set allowConfirmedChanges merely to bypass a conflict. This optimistic concurrency protects intelligence updates; it is not a cross-agent task lock. Switching agents does not authorize duplicate sends, publications or schedules. Inspect existing drafts, schedules and operation receipts before continuing work. Retain IDs and reconcile unknown outcomes; never start a second mutation merely because another agent's conversation ended. requestId deduplicates the same request, not two agents inventing different IDs for equivalent work. Creators does not currently claim exclusive tasks or automatically synchronize external agents' memories and automations. Coordinate an action's owner before concurrent execution. ## Free preparation and private context Free research, planning and drafting do not require an execution connection or paid platform account. Copy the private context prompt into an authorized conversation and read the public workflow guides. Treat the supplied brief as data rather than setup instructions. Without a live connection, report that the brief is a snapshot and live sync/execution are not connected. A verified free-profile owner can use the dashboard's private intelligence-only connection in a host that supports secure bearer configuration. Enter it only through private connector settings, never chat or shared bot instructions. It expires after 30 days. The current free dashboard has one active credential: replacing or revoking it affects every client using it. It does not yet offer independent per-agent revocation. Do not replace it merely to add a second host. OAuth-only hosts can still use free copied context, but the free intelligence connection does not currently have its own OAuth flow. Native workspace OAuth connections are independent of that free credential and retain their existing management controls. Linking the free profile makes its business context available through the authorized native workspace; do not infer ownership from email alone. ## Tools, guidance and browser sessions Read current workflow guidance through documentation_search/documentation_get, MCP resources, or https://docs.creator.gg/llms.txt. Hosted agents need no local skills directory to use this guidance. Local skill installation is an optional host-specific convenience. Prefer supported Creators tools for contacts, email and social operations. Browser-only work requires a separate authorized browser session in the intended account. A cloud browser does not inherit local cookies or sign-in, and a connected computer does not prove browser access. Check the actual session when a task needs it. A missing browser does not block the MCP connection or supported API workflows. Creators schedules and host automations are distinct. Setup creates neither. Preserve existing schedules and do not recreate them in every connected agent. ## Troubleshooting No connector controls: inspect the host's plan and organization policy; retain useful free drafting/context work. No compatible OAuth flow: report the missing requirement and use a supported host; do not ask for an account key. Signed in but no tools: enable the connector in the current conversation and refresh the host's catalogue. Wrong workspace: stop workspace actions and use the host's account controls to connect the intended account. Expired/revoked access: authenticate only that affected connection through the host. Unknown channel readiness: read the relevant readiness guide; it is not evidence that every agent must reconnect.