Codex | Fluos

Codex uses two commands: one to register the Streamable HTTP server, and one to start the OAuth flow.

You still approve OAuth

codex mcp add writes config. codex mcp login fluos opens the Fluos browser sign-in. Do not put credentials in the prompt.

One-prompt setup

Paste this into Codex:

Connect this coding environment to the Fluos Video MCP.

Run these exact commands in the terminal:
codex mcp add fluos --url https://www.fluos.io/api/v1/mcp/app --oauth-client-id vZg47Po1X1v3rHtU
codex mcp login fluos

Confirm the connection with "codex mcp list". If the browser asks for OAuth approval, pause and tell me what to approve. Once connected, use Fluos to list my workspaces. Do not ask me to edit config manually unless the commands fail.

Manual fallback

codex mcp add fluos --url https://www.fluos.io/api/v1/mcp/app --oauth-client-id vZg47Po1X1v3rHtU
codex mcp login fluos

codex mcp login fluos starts the OAuth flow. Approve Fluos in the browser, then return to the terminal. --oauth-client-id is Fluos's public Clerk OAuth client. There is no client secret.

Verify

codex mcp list

You should see fluos pointed at https://www.fluos.io/api/v1/mcp/app. Ask Codex to list your Fluos workspaces. If that fails with 401, run codex mcp login fluos again.

Optional: Docs MCP

codex mcp add fluos-docs --url https://www.fluos.io/api/v1/mcp

No 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 add succeeds but tools never appear, run login again and confirm the browser flow completed on the same machine.

Next: run a first video.