feat(vscode): revamp 15 MCP extensions around hosted HTTP endpoint

[acedatacloud-dev]

Summary

Every <service>/vscode/ extension in the MCPs monorepo was using the same broken clone-template. Three concrete user-visible issues:

1. READMEs lied about prompting for an API token. The package.json had env: { ACEDATACLOUD_API_TOKEN: "" } and no inputs block, so VS Code never asked. First call → silent 401 → 1-star review.
2. The hosted streamable-HTTP endpoint was never mentioned, even though it's the recommended zero-install path. Suno's main README documents https://suno.mcp.acedata.cloud/mcp + Claude.ai OAuth, but suno/vscode/README.md only knew about uvx mcp-suno.
3. "Zero-install setup" was false — uvx itself requires uv to be installed.

Plus duplicate-clone READMEs across 15 services with zero per-service tool list, examples, or pricing info.

What's in this PR

A small codegen tool — scripts/build_vscode_extensions.py + scripts/vscode_extensions.yaml — and the 45 files (15 × 3) it regenerated:

• <service>/vscode/package.json
  • Contributed MCP server is now type: "http" pointing at https://<alias>.mcp.acedata.cloud/mcp
  • headers.Authorization: "Bearer ${input:acedatacloud_api_token}" references a contributes.inputs promptString (password = true), so VS Code shows a secure prompt on first use and stores the token in the OS secret store
  • Version bumped 0.1.0 → 0.2.0, adds galleryBanner, per-service keywords/categories
• <service>/vscode/README.md
  • Hosted-endpoint-first quick start (3 steps)
  • Per-service example prompts (hand-curated, 2–3 each)
  • Tool reference table imported automatically from each service's main README — no more drift between docs and marketplace
  • Supported models list (where applicable), pricing/free-credit note
  • Documents the two alternatives clearly: local stdio via uvx <pypi-pkg>, and OAuth 2.1 via DCR
• <service>/vscode/.vscodeignore — standardised

15 services covered: suno, midjourney, flux, seedream, nanobanana, luma, sora, veo, kling, hailuo, wan, seedance, producer, serp, shorturl.

Why a codegen script instead of 15 hand edits

So the next person editing the marketplace listing for one MCP doesn't accidentally let it drift from the other 14, and so adding a new MCP is a one-line YAML entry. Tool counts and descriptions are parsed straight out of each main README.md's "## Tool Reference" table, so updates to upstream READMEs propagate.

Sanity checks

• python3 -c "import json; json.load(open('<svc>/vscode/package.json'))" — all 15 valid

• Tool counts per service:

  Service	Tools		Service	Tools
  suno	27		luma	8
  midjourney	15		sora	10
  producer	18		kling	8
  serp	11		hailuo	6
  flux	6		wan	7
  seedream	6		seedance	7
  nanobanana	4		veo	8
  shorturl	4

Out of scope (follow-ups)

• Duplicate icon.png across flux/kling/producer/wan (md5 f3551b1e…) and hailuo/luma (md5 2d8f5e5e…) — needs design assets.
• Missing extensions for aichat and openai — these are the highest-traffic services and have no vscode/ folder. Worth a separate PR.

Test

Locally:

python3 scripts/build_vscode_extensions.py --dry-run     # diff-only mode
python3 scripts/build_vscode_extensions.py --only suno   # regenerate one

Marketplace install: install the published acedatacloud.mcp-suno 0.2.0, open Copilot Chat, ask "generate a lofi track about late-night coding, use suno" → VS Code prompts for the API token → first call to the hosted endpoint succeeds.