Overview
Cloud-linked mode uses a local runner plus a source-scoped runner token. The MCP server can fetch approved adapter tools from Synapsor Cloud, delegate model-facing tool calls to Cloud capability APIs, claim approved writeback jobs, and submit applied/conflict/failed receipts.
`synapsor cloud connect` verifies the runner token, registers runner id/version/source/engine/capability metadata, and posts a heartbeat. It does not upload database URLs, passwords, write credentials, prompts, or table data.
Cloud mode is not required for the local demo. Use it when a team needs approval queues, RBAC, hosted replay/search, policy management, source-scoped runner tokens, and operational visibility.
Developer notes
- Use source-scoped runner tokens, not normal user API keys.
- Do not give runner tokens proposal approval permission.
- Keep database read/write credentials in the runner environment.
- Treat local and Cloud histories as separate unless you explicitly import them later.