feat: map add-mcp hosts added after 2.0 - #4
Merged
Conversation
CI installs add-mcp without a lockfile. 2.1.0 added kilo-code and later releases added fx, kimi-code, kiro-cli, mastracode, and pi, so the catalog-coverage test failed on main after a docs-only push. Co-authored-by: Kent C. Dodds <me+github@kentcdodds.com>
kentcdodds
marked this pull request as ready for review
September 11, 2026 22:42
Owner
Author
|
bugbot run |
|
Skipping Bugbot: Bugbot is disabled for this repository. Visit the Bugbot dashboard to update your settings. |
|
🎉 This PR is included in version 1.2.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
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
3 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.
Problem
The
validatejob onmainfailed at run 32588308071 (main (lts/*)), dated 2026-08-22. Install and Node setup succeeded.npm run validatefailed one test:This was not caused by the docs commit (
docs: recommend MCP install over long-term CLI use (#3)). CI installsadd-mcpwithout a lockfile (^2.0.0).add-mcp@2.1.0published the same day (~30 minutes earlier) addedkilo-codetogetAgentTypes(). Later 2.2–2.4 releases also addedfx,kimi-code,kiro-cli,mastracode, andpi, so a kilo-only skip would fail again today.Fix
Map every current
add-mcpagent (except the existing intentional Claude Desktop skip) and bump the dependency to^2.4.0:kilo-code(aliaseskilo,kilocode)kimi-code(aliaskimi)kiro-cli(aliaskiro)mastracode(aliasmastra)fxpi(aliaspi-agent)kody install --clients …writes these throughadd-mcpthe same way as Windsurf/Zed/Cline. Detection matches local process names; config paths follow the add-mcp 2.4 docs.Risk
Medium. New install targets, but writing goes through add-mcp (already the catalog owner). No login/MCP protocol changes.
Verify
npm run validatelts/-1,lts/*,latest