Flux Image Generator

Created By
frankdenoa year ago
Overview

what is Flux Image Generator?

Flux Image Generator is an MCP (Model Context Protocol) server designed for generating images using Black Forest Lab's FLUX model, allowing users to create images based on text prompts.

how to use Flux Image Generator?

To use the Flux Image Generator, you need to install the server, set up your Black Forest Lab API key, and start the server. You can then send text prompts to generate images.

key features of Flux Image Generator?

  • Generate images from text prompts
  • Customize image dimensions and settings
  • Batch generation of images from multiple prompts
  • Save generated images locally

use cases of Flux Image Generator?

  1. Creating unique artwork based on user-defined descriptions.
  2. Generating images for marketing materials or social media posts.
  3. Assisting developers in creating visual content for applications.

FAQ from Flux Image Generator?

  • What are the prerequisites for using Flux Image Generator?

You need Node.js (v18.0.0 or higher) and a Black Forest Lab API key.

  • Can I generate multiple images at once?

Yes! You can use the batch generation feature to create images from a list of prompts.

  • How do I customize the image generation settings?

You can specify parameters like width, height, and safety tolerance when generating images.

Server Config

{
  "mcpServers": {
    "flux-image-generator": {
      "command": "mcp-server-flux-image-generator",
      "env": {
        "BFL_API_KEY": "your_api_key_here"
      }
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
frankdeno
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago