Perchance MCP Lite
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Perchance MCP Lite generate an image of a cyberpunk city at night"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Perchance MCP Lite - Under 512MB RAM (No Browser)
For Render Free Tier 512MB - Uses external Byparr/Camoufox solver on separate Render account
Main MCP needs 1-2GB for Chromium (SeleniumBase UC). This lite version stays 80-120MB by offloading Turnstile solving to a separate service.
Architecture - Split for 512MB
Render Account 1 (512MB, 750h) - perchance-mcp-lite (this repo)
- 80-120MB RAM, no browser
- Only curl_cffi + httpx + mcp + fastapi
- Calls solver via SOLVER_URL env var
- Endpoints: /sse, /mcp, /ping (health)
Render Account 2 (512MB, 750h) - perchance-solver (separate repo)
- 250-350MB RAM, Camoufox Firefox stealth (Byparr)
- Solves Turnstile sitekey 0x4AAAAAAAA8g8NphwaSOT59
- Returns userKey + generates images via curl_cffi
- Endpoints: /solve, /generate, /ping, /v1 (FlareSolverr-compatible)
- Docker: ghcr.io/thephaseless/byparr:latest or custom solver.pyEach Render workspace has 750h/month free, so 2 accounts = 1500h total, both can be kept alive via UptimeRobot.
Related MCP server: Cloudflare Image MCP
Why Byparr/Camoufox?
FlareSolverr official v3.5.2 fixed Turnstile in #1634 but still Chromium + undetected-chromedriver = 400MB+ and detectable
Byparr = custom fork using Camoufox Firefox - C++ fingerprint patches (not JS), 0% detection on CreepJS, BrowserScan, 200MB vs 400MB+, 2-5x better success rate on Turnstile in 2026 benchmarks
Unlimited: Self-hosted, no Browserless 1000/mo limit
Quick Start
1. Deploy Solver (Render Account 2)
cd /home/user/perchance-solver
# Push to GitHub perchance-solver repo
git init && git add . && git commit -m "Byparr solver" && git push
# Render → New Web Service → Connect repo → Docker → Port 8000 → Health /ping → Free 512MB
# URL: https://perchance-solver.onrender.com
# Test: curl https://perchance-solver.onrender.com/ping → {"status":"ok"}Keep alive solver:
UptimeRobot free → Monitor
https://perchance-solver.onrender.com/pingevery 5 min
2. Deploy Lite MCP (Render Account 1)
cd /home/user/perchance-mcp-lite
# Push to GitHub perchance-mcp-lite repo
# Render → New Web Service → Docker → Port 8000 → Health /ping → Free 512MB
# Env vars:
# SOLVER_URL=https://perchance-solver.onrender.com
# PORT=8000
# URL: https://perchance-mcp-lite.onrender.com
# Test: curl https://perchance-mcp-lite.onrender.com/pingKeep alive lite:
UptimeRobot → Monitor
https://perchance-mcp-lite.onrender.com/pingevery 5 min
3. Connect MCP Clients
{
"mcpServers": {
"perchance-lite": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://perchance-mcp-lite.onrender.com/sse"]
}
}
}Or for solver direct (if you want images directly from solver):
{
"mcpServers": {
"perchance-solver": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://perchance-solver.onrender.com/sse"]
}
}
}Tools (same 15 as full MCP, but lite)
generate_image- Main: calls solver if SOLVER_URL set, else needs PERCHANCE_USER_KEYget_user_key_status- Check cached key + solver healthget_ad_code- Ad code via curl_cffi (no browser, unlimited)list_styles,get_generator_info,generate_batch
Env Vars
SOLVER_URL- https://your-solver.onrender.com (Byparr/Camoufox solver on separate Render account) - recommended for 512MBPERCHANCE_USER_KEY- 64-char hex from browser localStorage (manual, no solver, valid 30s IP-bound)PORT- Render sets automatically (8000)
Memory
Lite MCP: 80-120MB (no browser) - fits Render 512MB
Solver: 250-350MB (Camoufox) - fits separate Render 512MB
Full MCP: 800MB-1.5GB (SeleniumBase UC) - needs 2GB, OOM on Render
How it works
Lite:
get_ad_code_via_curl_cffi()- TLS impersonationimpersonate="chrome", bypasses JA3, 200 OK 64 hex, no browserLite: If no cached userKey,
POST SOLVER_URL/solve→ solver launches Camoufox, solves Turnstile0x4AAAAAAAA8g8NphwaSOT59, callsverifyUser?browserId&token&thread=0→ userKey 64 hexLite: Option A - Generate via
POST SOLVER_URL/generate(solver does curl_cffi generate + download, returns base64, same IP as solve, no invalid_key) Option B - Generate via curl_cffi directly (if userKey IP matches Lite IP - may fail if solver IP != lite IP, so Option A recommended)Download via curl_cffi immediate (token single-use expires 5min, IP-bound)
FlareSolverr-compatible API
Solver also exposes /v1 for drop-in Byparr/FlareSolverr clients:
curl -X POST https://perchance-solver.onrender.com/v1 -H "Content-Type: application/json" -d '{
"cmd": "request.get",
"url": "https://image-generation.perchance.org/embed",
"maxTimeout": 60000
}'
→ {"status":"ok","solution":{"cookies":[...],"userAgent":"...","response":"<html>..."}}Custom Fork - How we got Turnstile solving
Official FlareSolverr v3.5.2 fixed Turnstile in PR #1634
Byparr is custom fork using Camoufox Firefox (C++ patches, not JS) - better fingerprint, 200MB
For Perchance, we built custom solver that does exactly
turnstile.render({sitekey: '0x4AAAAAAAA8g8NphwaSOT59'})→ token → verifyUser → userKeyDocker:
ghcr.io/thephaseless/byparr:latestis drop-in, no custom code needed for generic, but custom solver returning userKey is more reliable for Perchance
Test Lite
pip install -r requirements.txt
export SOLVER_URL=https://perchance-solver.onrender.com
python server.py
# or
python -m uvicorn remote_server:app --host 0.0.0.0 --port 8000Available Tools
6 toolsgenerate_batchC
Generate multiple images via lite mode.
Inputs: prompts (required), seed, save_dir, art_style, +3 more. Returns: result
generate_imageA
Generate an image via lite mode (curl_cffi + external solver).
Memory: 80-120MB (no browser). If SOLVER_URL set, calls solver service (Byparr/Camoufox) that does Turnstile solving (200MB) on separate Render account. If no solver, requires PERCHANCE_USER_KEY env var (64 hex from browser).
Args: prompt: What to draw negative_prompt: Things to avoid seed: -1 random or specific int resolution: 512x512, 512x768, 768x512, 768x768 guidance_scale: 1-30 default 7 art_style: Optional style from list_styles save_path: Where to save (default auto)
Returns JSON with saved_path, seed, etc.
Inputs: prompt (required), seed, art_style, save_path, +3 more. Returns: result
get_ad_codeA
Get current ad access code via curl_cffi (no browser, unlimited).
Inputs: no named parameters. Returns: result
get_generator_infoB
Get information about the generator and lite mode.
Inputs: no named parameters. Returns: result
get_user_key_statusA
Check if cached userKey is valid and solver status.
Inputs: no named parameters. Returns: result
list_stylesA
List all available art styles for Perchance Stable Diffusion.
Inputs: no named parameters. Returns: result
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 6 tools
Most tools have clear, distinct purposes: style listing, generator info, key status, ad code, and image generation. However, generate_image and generate_batch share the same core action and may cause agents to hesitate when choosing which suits a task, though their singular vs. batch nature provides adequate separation.
All tool names follow a consistent verb_noun pattern in snake_case: list_, get_, and generate_. Even the batch and single image tools share the generate_ prefix, making the set predictable and easy to navigate.
With 6 tools, this server is well-scoped for a lightweight Perchance image generation interface. Each tool maps to a distinct functional area (styles, generator info, auth status, ad access, single/batch generation) without unnecessary bloat.
The core workflow is covered: discover styles, check key validity, and generate single or batch images. Minor gaps exist—such as no explicit tool to set or refresh the user key (relying on env var/solver) and no ability to list or retrieve generated images—but these are reasonable for a 'lite' server.
Maintenance
Related MCP Connectors
MCP server for Flux AI image generation
MCP server for OpenAI API (chat completions, image generation, embeddings) via AceDataCloud
MCP server for Qwen Image 3 AI image generation
9 remote MCP servers on Cloudflare Workers for AI agents. Free tier + Pro API keys.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceAn MCP server for AI-powered image processing (generate, edit, vary, analyze) supporting OpenAI, Gemini, Ideogram, and custom relay endpoints.-
- AlicenseNot gradedqualityDmaintenanceImage generation MCP server running on Cloudflare Workers, supporting multiple models like FLUX and SDXL with OpenAI-compatible endpoints.MIT
- FlicenseAqualityDmaintenanceStandalone MCP server and CLI for generating images via ChatGPT backend, with reliable exact file paths and multi-account login support.25-
- AlicenseNot gradedqualityDmaintenanceMCP server for AI-powered image generation using OpenAI's gpt-image-1 and gpt-image-2 models with advanced text rendering and native transparency support.1MIT