OAuth and access
Clerk OAuth for the Fluos Video MCP, scopes, and who can create videos.
Video MCP discovery:
Scopes: profile, email. Unauthenticated calls return 401 plus WWW-Authenticate. The host should start the browser flow from that challenge.
A pasted setup prompt cannot skip this step. The agent writes config. You approve Fluos in the browser.
Public OAuth client
Hosts should use Fluos's registered Clerk OAuth application. It is a public client — there is no secret.
| Field | Value |
|---|---|
| Client ID | vZg47Po1X1v3rHtU |
| Scopes | profile, email |
Pass it as --client-id in Claude Code, --oauth-client-id in Codex, or auth.CLIENT_ID in Cursor-style mcp.json. See Claude Code, Codex, and Cursor.
Who can call what
| Caller | Docs MCP | Video MCP |
|---|---|---|
| Anonymous | Yes | 401 |
| Signed-in free plan | Yes | 402 / PLAN_REQUIRED plus a billing URL (upgrade_fluos) |
| Pro / Enterprise | Yes | Yes |
| Collaborator on a paid workspace | Yes | Yes, if they can already spend on that workspace |
Credits charge the workspace owner, same as the dashboard. MAX-class generation is always on for this surface.
On PLAN_REQUIRED or CREDITS_EXHAUSTED, stop and show the user the billing URL. See Plans and Credits and Fluos API authentication.
Host checklist
- Register
https://www.fluos.io/api/v1/mcp/appas a Streamable HTTP server namedfluos, using client IDvZg47Po1X1v3rHtU. - On
401, followWWW-Authenticateand complete browser OAuth. - Retry the original tool call with the access token.
- If the plan is free, surface the billing URL instead of retrying forever.
Prefer the public client ID above. Dynamic client registration remains advertised on the authorization server metadata for hosts that still need it. See Fluos API authentication for the HTTP API bearer-token path.