AceDataCloud MCPs

Monorepo for all AceDataCloud MCP (Model Context Protocol) servers.

Servers

Directory	Standalone Repo	PyPI Package	Category	Documentation
acedatacloud/	AceDataCloudMCP	mcp-acedatacloud	Account	Documentation
face/	FaceTransformMCP	mcp-face-transform	Vision	Service details
fish/	FishMCP	mcp-fish	Audio	Documentation
flux/	FluxMCP	mcp-flux-pro	Image	Documentation
hailuo/	HailuoMCP	mcp-hailuo	Video	Documentation
happyhorse/	HappyHorseMCP	mcp-happyhorse	Video	Documentation
kling/	KlingMCP	mcp-kling	Video	Documentation
luma/	LumaMCP	mcp-luma	Video	Documentation
maestro/	MaestroMCP	mcp-maestro	Video Production	Documentation
midjourney/	MidjourneyMCP	mcp-midjourney	Image	Service details
nanobanana/	NanoBananaMCP	mcp-nanobanana-pro	Image	Documentation
producer/	ProducerMCP	mcp-producer	Music	Documentation
seedance/	SeedanceMCP	mcp-seedance	Video	Documentation
qwen-image/	QwenImageMCP	mcp-qwen-image	Image	Documentation
seedream/	SeedreamMCP	mcp-seedream-pro	Image	Documentation
serp/	SerpMCP	mcp-serp	Search	Documentation
shorturl/	ShortURLMCP	mcp-shorturl	Utility	Documentation
suno/	SunoMCP	mcp-suno	Music	Documentation
veo/	VeoMCP	mcp-veo	Video	Documentation
wan/	WanMCP	mcp-wan	Video	Documentation
aichat/	AiChatMCP	mcp-aichat	Chat	Documentation
discord-bot/	DiscordBotMCP	mcp-discord-bot	Messaging	Documentation
glm/	GLMMCP	mcp-glm	Chat	Documentation
grok/	GrokMCP	mcp-grok	Video	Documentation
minimax/	MinimaxMCP	mcp-minimax	Video	Documentation
openai/	OpenAIMCP	mcp-openai	AI APIs	Documentation
webextrator/	WebExtratorMCP	mcp-webextrator	Web & Data	Documentation

Retired

Directory	Standalone Repo	PyPI Package	Status
sora/	SoraMCP	mcp-sora	Retired; retained for historical reference

Publishing

Each MCP is published to multiple channels automatically on every push to main:

Channel	Status
PyPI	Active servers published
VS Code Marketplace	Active extensions published
JetBrains Marketplace	Active plugins published
Smithery	Active servers published
MCP Registry	Active servers published

Versioning uses CalVer (YYYY.M.D.BUILD), auto-generated at publish time.

How It Works

Sync Pipeline

AceDataCloud/Docs (OpenAPI specs)
     │  push to main
     ▼
dispatch-on-push.yml ──► docs-updated event
     │
     ▼
MCPs/sync-from-docs.yml ──► creates issue for Copilot
     │                       Copilot compares specs, opens PR
     ▼                       PR auto-merged
MCPs/sync-to-repos.yml ──► pushes to standalone repos
     This is a monorepo with MCP servers in subdirectories (luma/, suno/, midjourney/, flux/, etc.).
     │
     ▼
<Repo>/publish.yml ──► PyPI, VS Code, JetBrains, Smithery, MCP Registry

Rules

• This monorepo is the source of truth. Do not edit standalone repos directly.
• The mapping between subdirectories and standalone repos is defined in sync.yaml.
• CI runs lint (ruff) and tests (pytest, Python 3.10/3.11/3.12) on every push and PR.

Development

cd <server>/
pip install -e ".[dev]"
pytest --cov=core --cov=tools
ruff check .