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
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

6 hours ago