Choose credentials for the access they actually grant. Browser OAuth, personal tokens, organization service keys, Worker secrets, and temporary launch credentials serve different purposes and should not be exchanged for one another.
Interactive agent access#
Use browser OAuth for a normal Claude Code, Codex, or supported MCP connection. The service supports read and write hosting permissions; the granted scope determines which tools are available. The connection also needs current access to the selected organization.
Run list_organizations and explicitly choose the workspace when several are available. A site slug selects an operational target inside that workspace; it is not a credential or a separate authorization boundary.
Review MCP settings under Your connected agents. Disconnect revokes that OAuth application's access across all organizations approved for that connection. Reconnect through browser sign-in when access is needed again.
Headless credentials#
Personal tokens are available under the advanced Personal tokens section in MCP settings. They act as the issuing person in that organization, follow membership, and remain active until revoked unless an expiry was configured. Copy a new token when it is shown; it is not displayed again. Store it in the script environment or a secret store and revoke it when no longer needed.
Organization service/hosting keys are a separate path for supported automation. A second organization key does not create a site-only access boundary. Use the workspace/access arrangement appropriate to the customer rather than sharing broad credentials between unrelated customers.
Integration and temporary secrets#
| Value | Handling |
|---|---|
| Organization and site IDs | Public routing identifiers; do not treat them as secret authentication. |
Cloudflare SHARED_SECRET |
Store as a Worker Secret and match the server's integration value. |
| Signed artifact upload URL | Temporary capability; use it privately for its intended upload. |
| Guest build token | One reserved site, up to 24 hours and six deploy starts; ends when claimed. |
| Setup-status token | Limited to observing the launch ownership handoff. |
| Request key or private claim link | Keep private; preserve the request key for supported recovery. |
Do not put these secrets in source control, public CMS content, screenshots, logs, deployment ZIPs, or downloadable source archives. A public setup continuation link shown privately in the owning chat is different from the emailed private claim link.
Recover from exposure#
Revoke the affected connection or token through the supported settings. For a Worker secret or inaccessible temporary credential, contact support to coordinate replacement or recovery. Remove the exposed value from active configuration and investigate where it was published. Creating a replacement site does not revoke the old access.
Verify the replacement connection with a read-only organization/site inventory before resuming changes. See authentication and data handling.