Skip to main content
Glama
rocnubie

Flux-2 Online MCP

by rocnubie
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
JavaScript
Remote

Flux-2 Online MCP Server

Flux-2 Online - Flux 2 AI Image Generator

MCP Badge License: MIT Node MCP

A Model Context Protocol server that exposes the canonical Flux-2 Online knowledge surface — image generation workflows and styles, pricing, FAQ, official links — to MCP-compatible AI clients such as Claude Desktop, Cursor, Windsurf, and Continue. Read-only, no API keys, no quota, ~50 ms cold start.

Official website: https://flux-2.online

🎨 About Flux-2 Online

Flux-2 Online is a web-based AI image and video generation platform built around the Flux family of models. Users describe what they want in a text prompt, choose a model suited to their needs — from the fast and budget-friendly Flux 2 Dev to the higher-fidelity Flux 2 Pro or the flexible Flux 2 Flex — and receive generated images within seconds. Beyond text-to-image, the platform bundles a set of editing tools: image-to-image transformation, face swap, background removal, image enhancement, and image-to-video conversion, all accessible from a single browser-based interface with no local installation required.

Related MCP server: Muse AI Image MCP Server

Key Features

  • Multiple Flux model tiers — Flux 2 Dev for speed, Flux 2 Pro for quality, Flux 2 Flex for granular control, plus additional models like Seedream and Qwen for complex text rendering.

  • LoRA styles library — A curated collection of artistic styles spanning anime, photorealism, and more, selectable at generation time to steer the visual aesthetic without prompt engineering alone.

  • Kontext consistency mode — Keeps character appearance and object details coherent across a sequence of generated images, useful for multi-panel or narrative work.

  • Bundled editing tools — Face swap, hairstyle modifier, text remover, background changer, professional photo generator, and product photography generator are included alongside the core image generator.

  • Image-to-video conversion — Powered by Seedance 1.0 Lite, the platform converts still images into short video clips with configurable duration and resolution settings.

  • API access — A RESTful API with webhook support lets developers integrate image generation into their own applications using Python, JavaScript, or any HTTP client.

  • Free tier with daily credits — Basic generation is available without a subscription; a credit-based system scales up to commercial-grade output, higher resolutions, and batch processing.

Use Cases

  • Content creation — Social media managers and bloggers generate on-brand illustrations or photography-style images from text prompts, bypassing stock photo licensing.

  • E-commerce product visuals — Store owners use the product photography generator and background tools to produce clean, professional product shots without a physical studio.

  • Concept iteration — Designers test visual directions quickly by generating multiple style variants in parallel before committing to a final look.

  • Short-form video assets — Marketers convert finished images into brief animated clips suitable for social ads, reels, or presentation slides.

  • Developer integration — Independent developers embed the API into creative apps, chatbots, or internal tools that need on-demand image generation without managing their own model infrastructure.

Who Is It For

Flux-2 Online targets a broad range of creators and builders who need AI-generated visuals without the overhead of running models locally. Graphic designers and marketing professionals will find the multi-model selector and LoRA library useful for iterating on visual styles quickly. E-commerce operators benefit from the dedicated product photography and background editing tools. Developers who want image generation as a service rather than a self-hosted pipeline can connect via the RESTful API. The free daily credit allowance also makes the platform accessible to individual hobbyists and students who want to explore AI image generation before committing to a paid plan.

Tools

list_styles

Return the canonical list of image-generation styles or presets the site exposes. (Flux-2 Online)

Input: no parameters. Returns: text/markdown.

get_pricing

Return the canonical pricing entry point for Flux-2 Online.

Input: no parameters. Returns: text/markdown.

get_official_links

Return the canonical list of official links for Flux-2 Online (website, support, docs when available).

Input: no parameters. Returns: text/markdown.

Resources

  • site://flux-2-online/styles — Supported image-generation styles and presets.

  • site://flux-2-online/pricing — Canonical pricing entry point.

  • site://flux-2-online/faq — Short FAQ generated from public site metadata.

  • site://flux-2-online/links — Canonical URLs to share with users.

Prompts

tell_me_about_flux_2_online

Summarize what the site is, who it's for, and how it works. — Flux-2 Online

try_image_style_flux_2_online

Recommend a starting image-generation style for a stated goal. — Flux-2 Online

Installation

Install via Smithery

npx -y @smithery/cli install flux-2-online-mcp --client claude

(Replace claude with cursor, windsurf, or continue for those clients.)

Install from source

git clone https://github.com/rocnubie/flux-2-online-mcp.git
cd flux-2-online-mcp
pnpm install

Then add to your MCP client config (claude_desktop_config.json for Claude Desktop, mcp.json for Cursor / Windsurf / Continue):

{
  "mcpServers": {
    "flux-2-online-mcp": {
      "command": "node",
      "args": [
        "/absolute/path/to/flux-2-online-mcp/src/index.mjs"
      ]
    }
  }
}

Debug with MCP Inspector

npx @modelcontextprotocol/inspector node src/index.mjs

Official Links

Development

pnpm install
pnpm start                 # run the server over stdio

License

MIT

Available Tools

3 tools
get_pricingB

Return the canonical pricing entry point for Flux-2 Online.

ParametersJSON Schema
NameRequiredDescriptionDefault

No parameters

TDQS

B3/5.0
Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description bears full responsibility for behavioral disclosure, but it only states the basic purpose. No information about side effects, rate limits, authentication needs, or output format is given.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, clear sentence with no extraneous words. Every part contributes to understanding the tool's core function.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite being a simple tool with no parameters, the description lacks details about the output format or how the returned pricing entry point should be interpreted. It is adequately clear but not fully complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has 0 parameters and schema coverage is 100%, so the description's mention of returning a 'canonical pricing entry point' adds meaningful context beyond the empty schema, earning a baseline of 4.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'Return' and the specific resource 'canonical pricing entry point for Flux-2 Online', but the exact nature of the return value (e.g., a URL, a document, a price list) is slightly ambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus siblings like list_styles or get_official_links. There is no mention of prerequisites, context, or exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

list_stylesA

Return the canonical list of image-generation styles or presets the site exposes. (Flux-2 Online)

ParametersJSON Schema
NameRequiredDescriptionDefault

No parameters

TDQS

A4/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description must carry the full burden. It states that the tool returns a list, but does not disclose potential caching, data freshness, or any limitations. The behavior is simple enough, but more context would be helpful.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise, consisting of a single clear sentence with an additional parenthetical for context (Flux-2 Online). No unnecessary words; every sentence earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given that there are no parameters and no output schema, the description is largely sufficient. It clearly states what the tool returns and the model context. However, it could mention how the styles might be used in image generation for further clarity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has no properties (0 parameters), and schema description coverage is 100%, so the baseline is 4. The description does not add parameter information, but none is needed since there are no parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it returns 'the canonical list of image-generation styles or presets,' using a specific verb and resource. This distinguishes it from sibling tools like get_pricing and get_official_links, which have different purposes.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit guidance on when to use this tool versus alternatives. While the purpose is clear, the description lacks information about prerequisites or context for use, leaving the agent to infer usage.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. 3 tool updatesv0.1.0
    • First observedget_official_links
    • First observedget_pricing
    • First observedlist_styles
Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

A3.7/5.0
Disambiguation5/5

Each tool targets a distinct aspect: styles, pricing, and official links. There is no overlap or ambiguity.

Naming Consistency5/5

All tools follow a consistent verb_noun pattern: list_styles, get_pricing, get_official_links. No mixing of conventions.

Tool Count4/5

Three tools is slightly on the low side but reasonable for a focused informational server. Each tool serves a clear purpose.

Completeness3/5

The server lacks tools for core actions like image generation or detailed style information, leaving notable gaps if the domain includes those features.

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/rocnubie/flux-2-online-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server