Repository navigation
Fix npx @edgegap/mcp failing to start (0.3.1) - #6
Merged
Merged
Conversation
0.3.0 added a second bin command, edgegap-mcp-http. With two commands and neither named "mcp", npx cannot choose one and exits with "could not determine executable to run", so every config using "args": ["-y", "@edgegap/mcp"], including the README's, broke. - bin is back to one command. The self-hosted HTTP server now starts with "edgegap-mcp --http" (npm run start:http). The Docker image still runs dist/http.js directly and is unaffected. Not adding an "mcp" command instead: it would collide with the MCP Python SDK's mcp CLI on a global install. - Add repository, homepage and bugs to package.json so npm links to the source. - test/package.mjs applies npm's own bin resolution rule and checks that every hardcoded version matches package.json. It fails on 0.3.0. - test/http.mjs now starts the server through --http. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
0.3.0 added a second bin command, edgegap-mcp-http. With two commands
and neither named "mcp", npx cannot choose one and exits with "could
not determine executable to run", so every config using
"args": ["-y", "@edgegap/mcp"], including the README's, broke.
with "edgegap-mcp --http" (npm run start:http). The Docker image still
runs dist/http.js directly and is unaffected. Not adding an "mcp"
command instead: it would collide with the MCP Python SDK's mcp CLI on
a global install.
source.
every hardcoded version matches package.json. It fails on 0.3.0.
Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com