Flux cf

Created By
Hzzy2Oa year ago
Overview

What is Flux Cloudflare MCP?

Flux Cloudflare MCP is a powerful Model Context Protocol (MCP) server that enables AI assistants to generate high-quality images using the Flux model via a Cloudflare Worker API.

How to use Flux Cloudflare MCP?

To use Flux Cloudflare MCP, you can either run it directly using NPX with your API token and URL or clone the repository and set it up locally. You need to deploy a Flux API endpoint to function properly.

Key features of Flux Cloudflare MCP?

  • High-quality image generation using the Flux model.
  • Seamless integration with AI assistants like Claude.
  • Customizable parameters for image generation.
  • Compatibility with any MCP client.
  • Secure local processing through Cloudflare Workers.
  • Ability to get text completions using the same API.

Use cases of Flux Cloudflare MCP?

  1. Generating images based on text prompts for creative projects.
  2. Integrating with AI assistants for enhanced functionalities.
  3. Customizing image generation parameters for specific needs.

FAQ from Flux Cloudflare MCP?

  • What is the Flux model?

The Flux model is a state-of-the-art image generation model developed by Black Forest Labs.

  • Is there a cost to use Flux Cloudflare MCP?

The usage of Flux Cloudflare MCP is free, but you may incur costs based on your Cloudflare usage.

  • Can I customize the image generation parameters?

Yes! You can customize parameters like aspect ratio and inference steps.

Server Config

{
  "mcpServers": {
    "Flux cf": {
      "command": "npx",
      "args": [
        "-y",
        "@smithery/cli@latest",
        "run",
        "@Hzzy2O/flux-cloudfare-mcp",
        "--config",
        "\"{\\\"fluxApiToken\\\":\\\"AIzaSyCb_wdwMQa_u3KHkd1ywHptTh_Rf07-bJU\\\",\\\"fluxApiUrl\\\":\\\"https://flux-api.capiiii664.workers.dev\\\"}\""
      ]
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Hzzy2O
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