✨ SiliconFlow FLUX MCP 服务器 ✨

Created By
snakeyinga year ago
A Python-based MCP server for SiliconFlow FLUX image generation. 一个基于 Python 的 MCP服务器,用于 SiliconFlow FLUX 图像生成。
Overview

What is Flux MCP Server?

Flux MCP Server is a Python-based server designed for generating images using the SiliconFlow FLUX series models. It operates as a standalone HTTP service, suitable for deployment in Docker containers or directly on physical/virtual machines.

How to use Flux MCP Server?

To use the Flux MCP Server, clone the repository, set up your environment, configure your SiliconFlow API keys, and run the server using the provided command. You can then connect your MCP client to the server to generate images.

Key features of Flux MCP Server?

  • 🎨 Core tool for image generation named generate_image.
  • 🤖 Support for multiple SiliconFlow FLUX models during image generation.
  • ⚙️ Configurable parameters for image aspect ratio, inference steps, guidance scale, and seed.
  • 🔑 API key polling for enhanced reliability and rate limit management.
  • 🛠️ Docker-ready with a provided Dockerfile for easy deployment.

Use cases of Flux MCP Server?

  1. Generating images for various applications using AI models.
  2. Supporting developers in creating visual content through automated image generation.
  3. Facilitating research in image processing and AI model performance.

FAQ from Flux MCP Server?

  • Can Flux MCP Server generate images from any model?

Yes, it supports various SiliconFlow FLUX models.

  • Is Flux MCP Server free to use?

Yes, it is open-source and free to use.

  • What are the system requirements?

Requires Python 3.11 or higher and a valid SiliconFlow API key.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
snakeying
Star
0
Language
Python
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)

20 hours ago
Gpt Scrambler

2 days ago