Other agents

Any host that supports remote Streamable HTTP and OAuth can use Fluos. The server name, URL, and auth are the same as Claude Code, Codex, and Cursor — only the config file format changes.

You still approve OAuth

The agent can write the config. You still approve Fluos in the browser. If the client cannot configure itself, it should show you the exact file and entry to add. Do not put credentials in the prompt.

One-prompt setup

Connect your MCP-compatible coding agent to Fluos.

Add a remote server named "fluos" using Streamable HTTP at:
https://www.fluos.io/api/v1/mcp/app

Use Fluos's public Clerk OAuth client ID vZg47Po1X1v3rHtU (no secret). Use your client's supported MCP configuration format and preserve all existing servers. If browser OAuth is required, pause and tell me what to approve. Once connected, call Fluos to list my workspaces. If this client cannot configure itself, show me the exact config file and entry to add.

Connection details

Name: fluos
Transport: Streamable HTTP
URL: https://www.fluos.io/api/v1/mcp/app
Authentication: Browser OAuth
OAuth client ID: vZg47Po1X1v3rHtU
Protocol: 2025-06-18

Discovery documents the host should read:

Unauthenticated calls return 401 plus WWW-Authenticate. The host should start the browser flow from that challenge. See OAuth and access.

Optional: Docs MCP

Name: fluos-docs
Transport: Streamable HTTP
URL: https://www.fluos.io/api/v1/mcp
Authentication: None

No login. This server cannot create videos. See Docs MCP.

Common host shapes

If your client uses an mcpServers map (Cursor-style):

{
  "mcpServers": {
    "fluos": {
      "url": "https://www.fluos.io/api/v1/mcp/app",
      "auth": {
        "CLIENT_ID": "vZg47Po1X1v3rHtU"
      }
    }
  }
}

If it uses a list of HTTP servers, register url, transport: "http" (or Streamable HTTP), and name fluos. Do not send a local command or stdio wrapper — Fluos is a remote server.

Verify

After OAuth, ask the agent to call list_workspaces. If tools never appear, confirm the host supports remote HTTP MCP (not only local stdio) and that it completed the OAuth challenge.

Next: run a first video.