docs: mcp-remote bridge install names a package that does not exist on npm - #122
Open
tonydzi wants to merge 1 commit into
Open
docs: mcp-remote bridge install names a package that does not exist on npm#122tonydzi wants to merge 1 commit into
tonydzi wants to merge 1 commit into
Conversation
docs/ide-setup.md told readers to run `npm install -g @modelcontextprotocol/client-cli` for the mcp-remote bridge. That package is not on npm (E404), while the config SLM itself generates for --transport http-mcp-remote uses `command: "mcp-remote"`. The binary lives in the npm package `mcp-remote`; three occurrences updated, docs only. Assisted-by: Claude (Anthropic)
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
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.
What was broken
docs/ide-setup.mdtells the reader to install themcp-remotebridge with:That package does not exist on npm, so the install cannot succeed:
(node 24.14.0, npm 11.9.0, isolated prefix)
Three occurrences, all in
docs/ide-setup.md: the transport table (line 17), the bridge install block (line 23) and the Grok CLI section (line 325). Nothing else in the repo references that name. It has been there since82484ff(2026-06-10, "docs: document dual HTTP + stdio MCP transports (v3.6.7)") — the documented path never worked.Why it blocks a real user, not just a link
SLM itself writes
mcp-remoteas the command, so the reader ends up with a config pointing at a binary the documented install can never provide. Running your own connector ona5438ee(Python 3.12):{"superlocalmemory": {"type": "stdio", "command": "mcp-remote", "args": ["http://127.0.0.1:8765/mcp/"]}}Same expectation is asserted in your tests (
tests/test_cli_subparsers/test_transport_connect.py, C-3/C-8:assert block["command"] == "mcp-remote"), andslm connect --transport http-mcp-remoteis a documented flag (cli/main.py).What it is now
The same three lines name
mcp-remote— the package that actually ships that binary:(mcp-remote 0.1.38 — the binary name matches the
commandyour connector writes.)Checks
tests/test_cli_subparsers/test_transport_connect.pyon this branch: 15 passed (Python 3.12). Identical result on unmodifiedmain— the change is docs-only, 3 lines, no code touched.If you would rather recommend
npx -y mcp-remote(no global install) in the IDE blocks, say the word and I will send that shape instead.