From the maker

Flux AI connects compatible AI assistants to image, video and music generation through a remote MCP server. Discover available models, estimate generation costs, submit tasks after user approval, and retrieve completed results. Connect using Streamable HTTP and OAuth. Generation uses Flux AI account credits. Setup instructions are available at https://fluxaipro.art/mcp.

How to connect

Streamable HTTP endpoint:

https://fluxaipro.art/api/mcp

What happened when we asked

We asked on 17 October 2026 and it challenged us for credentials. That is a working server guarding itself: it answered, and it wants an account we do not hold. A tool count and a response time come from a tools/list we were never served, so this listing carries neither.

How it asks you to sign in

Its refusal named a public document describing how to authenticate, which is what the MCP authorization spec asks a guarded server to publish. We read that document on 17 October 2026. Everything below is what it says; we have still not been inside this server.

It calls itself

Fluxship

Sign in through

clerk.fluxaipro.art

Token accepted in

header

Read

2026-10-17 03:20 UTC

The 3 permissions it declares

These are the scopes the document lists, verbatim. They describe what an account can grant this server, not what it will do with the grant, and we have not audited either.

• mcp:read
• mcp:generate
• mcp:upload

Anything above describes one moment on the date shown. We do not re-test on a schedule, so nothing here says what this server is doing now. We have not audited its code, its data handling or its permissions, and this is not a safety rating.