feat(vscode): bring face + fish into hosted-HTTP codegen#360
Merged
Conversation
face and fish were the only two MCP services whose VS Code extensions were still hand-written and shipping with the old `uvx <pkg>` stdio launch config — they never got the hosted-HTTP-first UX from #356. Add them to `scripts/vscode_extensions.yaml`: - face: pinned to existing IDs (`mcp-face-transform` on PyPI/Marketplace) via `pypi_override` and `ext_name`. Currently Alpha. - fish: defaults work (`mcp-fish` already matches `mcp-<alias>`). Regenerate `face/vscode/{package.json,README.md,.vscodeignore}` and `fish/vscode/{package.json,README.md,.vscodeignore}` from the codegen. Each now points to its hosted streamable-HTTP endpoint at `https://<alias>.mcp.acedata.cloud/mcp` with a Bearer token prompt input — no local Python install required. Also normalize the main READMEs' tool tables to `## Tool Reference` with `| Tool | Description |` columns so the codegen can parse them (was `## Available Tools` with `Tool|Endpoint|Purpose` on face, `## Available Tools` heading on fish). Marketplace IDs are unchanged so existing installs / ratings carry over: `acedatacloud.mcp-face-transform` and `acedatacloud.mcp-fish".
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
1 participant
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 + #358, 15/17 MCP services have their VS Code extensions auto-generated by
scripts/build_vscode_extensions.pyand ship with the new hosted streamable-HTTP UX (Bearer-token input, nouvxinstall needed). The two stragglers — face and fish — were still hand-written with the olduvx <pkg>stdio launch config.What this changes
scripts/vscode_extensions.yaml— add curated entries for face and fish:face: pinned to existing marketplace + PyPI IDs (acedatacloud.mcp-face-transform/mcp-face-transform) via the newpypi_override+ext_nameoverrides. Currently in Alpha.fish: defaults are already correct (mcp-fishmatchesmcp-<alias>).face/vscode/+fish/vscode/— regenerated from the codegen. Both now register an HTTP MCP server athttps://<alias>.mcp.acedata.cloud/mcpwith a password-protected token input, matching the other 15.face/README.md+fish/README.md— normalize the tool table to## Tool Reference/| Tool | Description |so the codegen can parse it. face also collapses its oldTool | Endpoint | Purposecolumns into a single Description column (endpoints aren't user-callable through MCP).Marketplace IDs are unchanged
acedatacloud.mcp-face-transformmcp-face-transformacedatacloud.mcp-fishmcp-fishExisting installs, ratings, and download counts carry over. Hardcoded
EXT_IDin each downstreampublish.ymlalready matches.Expected post-merge
Sync triggers downstream
FaceTransformMCPandFishMCP→ theirpublish.yml→ fresh CalVer2026.MMDD.<n>published to marketplace with the new UX. Will verify with marketplace API after merge.