Add Flux plugin

[acedatacloud-dev]

Summary

Add a separately searchable Flux third-party Cursor plugin. It reuses the existing Ace Data Cloud hosted flux MCP, a focused Agent skill, and the exact service logo from the Ace Data Cloud Flux integration. The English and Chinese guides cover installation, service API key, permissions, one first-run prompt, task retrieval where applicable, result inspection, Credits, and troubleshooting.

Standalone source is reviewable at AceDataCloud/FluxCursor#1 and its exact commit AceDataCloud/FluxCursor@8b49c51. This is a tool plugin, not a Cursor chat-model provider.

Validation

• Official node scripts/validate-plugins.mjs: passed with this marketplace entry.

• git diff --check: passed. Logo SHA-256: e1c93722db66db1f3721d4b1e02f1e63f130a6a41151476856e51fca914e7c94.

• Authenticated hosted MCP tools/list exposed flux_generate_image and flux_get_task; its live schema includes the first-run parameters. This is a read-only tool/schema check, not a claim of a new paid generation or a Cursor UI install.

• On 2026-10-12, an authenticated read-only task query against the hosted MCP returned a completed historical result and an HTTPS media URL. No new paid generation was submitted. This is direct MCP validation, not a Cursor Agent UI call or Marketplace installation.

Publication state

This PR is a formal submission. Review, merge, Marketplace listing and search, user installation, and a Cursor Agent call remain separate gates. Cursor 3.24.12 is signed in; this plugin's own UI installation and Agent call have not yet been verified. No credential is committed.

---

Note

Medium Risk
Introduces a third-party hosted MCP that uses user API keys and can trigger paid image-generation calls, but only adds marketplace metadata and plugin packaging with no changes to core Cursor code.

Overview
Adds a new Flux third-party Cursor plugin under third_party/flux/ and registers it in .cursor-plugin/marketplace.json and the root plugin table in README.md.

The plugin is a thin integration around Ace Data Cloud’s hosted HTTP MCP (flux_generate_image, flux_get_task). Users configure a required ACEDATACLOUD_API_TOKEN; mcp.json sends it as a Bearer header to https://flux.mcp.acedata.cloud/mcp. It ships with manifest metadata (Cursor 3.13.0+), an Agent skill, English/Chinese setup guides, a first-run prompt, and standard LICENSE / CHANGELOG files—no local server or core repo runtime changes.

^{Reviewed by Cursor Bugbot for commit 575d7c7. Bugbot is set up for automated code reviews on this repo. Configure here.}

README attribution: the shared English/Chinese CTA links are tagged with opensource / referral / evergreen, with service/Cursor/language content values. Matching source documentation is proposed at AceDataCloud/FluxCursor#2. This is a documentation-only update; source merge, official indexing, public search/install and measured activation remain separate gates.

2026-10-14 base refresh

Rebased onto current official main ce649c03ac3b75b6ae80cbd15b7e2c536caedb5a. The catalog and root README retain all 102 upstream entries and their existing content, plus this plugin's original entry. The plugin directory tree remains byte-for-byte identical (8879db750c9539a6497042c9553e99b00ee410d4), including its HTTP MCP config, API token declaration, skill, and bilingual UTM links.

Validation for the published tree 60b644fe18b7395be72cfa6c3eeceb387348cf25 at head e37037d63f362207bc7ea235088d952996cafb35: node scripts/validate-plugins.mjs and git diff --check pass, and merge-tree with the pinned base is clean. GitHub updateRefs was used with an atomic beforeOid lease after the ordinary Git HTTPS transport timed out. This maintains the existing submission; Marketplace approval, installation, and host acceptance remain separate stages.

2026-10-15 base refresh

Rebased onto current official main 850d7f2e9f5e55dff7eb00a0a479337fe79eb22f. The catalog and root README retain all 104 upstream entries and their existing content, plus this plugin's original entry. The plugin directory tree remains byte-for-byte identical (8879db750c9539a6497042c9553e99b00ee410d4), including its HTTP MCP config, API token declaration, skill, and bilingual UTM links.

Validation for the published tree 4f6cb4f00322029db06c8f80d129acc30f90f79d at head a4c8d25442051668cc0d4facf62afe7edf8f3e4d: node scripts/validate-plugins.mjs and git diff --check pass, and merge-tree with the pinned base is clean. GitHub updateRefs was used with an atomic beforeOid lease after the ordinary Git HTTPS transport timed out. This maintains the existing submission; Marketplace approval, installation, and host acceptance remain separate stages.

2026-10-18 native-distribution update

Updated onto current official main 101b274dd991f694e1f7024be2157e5f3adf07de. All 109 existing catalog entries and the full upstream README are preserved, including the revised Tailscale text. The plugin directory remains unchanged (8879db750c9539a6497042c9553e99b00ee410d4). This update only resolves the catalog/root README conflict against the latest official base.

Validation at 575d7c714d3ebd5a440fb050a1fd2923fa688bb4: current node scripts/validate-plugins.mjs, node scripts/generate-pstack-harness-trees.mjs --check, git diff --check and merge-tree pass. Published Git commit/tree SHAs equal the locally validated objects. Every original OPEN branch update uses atomic beforeOid comparison. No duplicate submission, PR merge, deployment, paid generation or publisher agreement acceptance. Official review, live service-name search, installation and actual Cursor use remain separate gates.

[cursor]

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

^{Bugbot Autofix is ON, but it could not run because the branch was deleted or merged before autofix could start.}

^{Reviewed by Cursor Bugbot for commit 0bc2a86. Configure here.}