Flux Image Generation Server

Created By
caoka year ago
flux image generation mcp server
Overview

what is Flux Image Generation Server?

Flux Image Generation Server is a simple HTTP server that utilizes the Replicate Flux Schnell model to generate images based on user-defined prompts.

how to use Flux Image Generation Server?

To use the server, first install the necessary dependencies, set your Replicate API token as an environment variable, and then run the server. You can generate images by sending a POST request to the server with a JSON payload containing your image description.

key features of Flux Image Generation Server?

  • Simple HTTP API for image generation
  • Utilizes the Replicate Flux Schnell model
  • Easy setup and configuration

use cases of Flux Image Generation Server?

  1. Generating custom images for creative projects
  2. Creating visual content for marketing and social media
  3. Rapid prototyping of image ideas based on textual descriptions

FAQ from Flux Image Generation Server?

  • What is required to run the server?

You need Node.js installed and a valid Replicate API token.

  • How do I generate an image?

Send a POST request to the /generate endpoint with your image description in the request body.

  • Can I run the server on a different port?

Yes, you can modify the server configuration to run on a different port.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
caok
Star
0
Language
JavaScript
License
Apache-2.0 license

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
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