fix(vscode): use mcp-<alias> as marketplace extension id#358
Merged
Conversation
The codegen was using the PyPI package name as the VS Code extension `name`. For flux/nanobanana/seedream the PyPI name is `mcp-<alias>-pro` (because `mcp-<alias>` was taken on PyPI), but the marketplace extension ids we already own are plain `mcp-<alias>`. Reusing the PyPI `-pro` suffix caused vsce publish to try a new id and fail with "This extension display name is taken" — keeping these three stuck on old versions while the other 12 auto-published successfully. Decouple the two namespaces: add a dedicated `ext_name` on Service defaulting to `mcp-<alias>` (overridable via `ext_name` in vscode_extensions.yaml). Regenerated package.json for flux, nanobanana, seedream — diff is the `name` field only.
Germey
approved these changes
May 31, 2026
This was referenced May 31, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
After #356 merged, 12/15 VS Code extensions auto-republished to the marketplace on
2026.531.0. Three did not: flux, nanobanana, seedream. The downstreampublish.ymlfor each ran and failed at thevsce publishstep with:Failing runs:
Root cause
scripts/build_vscode_extensions.pywas using the PyPI package name as the VS Code extensionname(pkg['name'] = svc.pypi_pkg). The two namespaces aren't the same:mcp-flux-pro(the bare name was taken on PyPI)acedatacloud.mcp-fluxmcp-nanobanana-proacedatacloud.mcp-nanobananamcp-seedream-proacedatacloud.mcp-seedreamPR #356 changed these from the old
mcp-<alias>tomcp-<alias>-pro, sovsce publishsaw a brand-new extension id and tried to create it, but the displayNameFlux MCP/NanoBanana MCP/Seedream MCPis already taken by the existing extension under the same publisher → 409.Fix
Decouple the two namespaces. Add
ext_nameto theServicedataclass, default it tomcp-<alias>(the convention already in marketplace), with anext_name:yaml override available for any future service where they diverge.Regenerated only the 3 affected
vscode/package.json— diff is thenamefield only. The other 12 services already hadpypi == mcp-<alias>so their codegen output is unchanged.Verification after merge
Once main triggers the sync, each of the three downstream repos will get a new push and their
publish.ymlshould produce a fresh CalVer2026.MMDD.0on the marketplace. Will verify with marketplace API after merge.