Claude Code
Connect Claude Code to the Fluos Video MCP with one terminal command, then approve browser OAuth.
Claude Code registers Fluos as a user-scoped HTTP MCP server. The same connection then works in every project.
You still approve OAuth
The command writes config. You still run /mcp and finish the Fluos browser sign-in. Do not put credentials in the prompt.
One-prompt setup
Paste this into Claude Code:
Connect this coding environment to the Fluos Video MCP.
Run this exact command in the terminal:
claude mcp add --scope user --transport http --client-id vZg47Po1X1v3rHtU fluos https://www.fluos.io/api/v1/mcp/app
Then verify the server with "claude mcp list". If browser OAuth or /mcp approval is required, pause and tell me exactly what to approve. Once connected, use Fluos to list my workspaces. Do not ask me to edit config manually unless the command fails.Manual fallback
claude mcp add --scope user --transport http --client-id vZg47Po1X1v3rHtU fluos https://www.fluos.io/api/v1/mcp/appThen:
- Start Claude Code.
- Run
/mcp. - Select fluos.
- Finish the browser sign-in.
--scope user registers the server once for all of your projects. --client-id is Fluos's public Clerk OAuth client. There is no client secret.
Verify
claude mcp listYou should see fluos pointed at https://www.fluos.io/api/v1/mcp/app. Ask Claude to list your Fluos workspaces. If that fails with 401, complete /mcp OAuth and retry.
Optional: Docs MCP
The Video MCP cannot search documentation. Add the public server as a second connection:
claude mcp add --scope user --transport http fluos-docs https://www.fluos.io/api/v1/mcpNo login. This server cannot create videos. See Docs MCP.
If it will not connect
- Confirm the URL is
/api/v1/mcp/app, not the public docs server. - Free plans receive
PLAN_REQUIRED. See OAuth and access. - If Fluos never appears after the command, run
claude mcp listand check for a merge conflict with an existingfluosentry.
Next: run a first video.