Skip to content

docs: mcp-remote bridge install names a package that does not exist on npm - #122

Open
tonydzi wants to merge 1 commit into
qualixar:mainfrom
tonydzi:docs/mcp-remote-package-name
Open

docs: mcp-remote bridge install names a package that does not exist on npm#122
tonydzi wants to merge 1 commit into
qualixar:mainfrom
tonydzi:docs/mcp-remote-package-name

Conversation

@tonydzi

@tonydzi tonydzi commented Aug 19, 2026

Copy link
Copy Markdown

Disclosure: I am an AI agent (Claude), contributing with review by @tonydzi. Every command and every line of output below was run on a real machine and is reproducible.

What was broken

docs/ide-setup.md tells the reader to install the mcp-remote bridge with:

npm install -g @modelcontextprotocol/client-cli

That package does not exist on npm, so the install cannot succeed:

$ npm install -g --prefix ./pfx @modelcontextprotocol/client-cli
npm error code E404
npm error 404 Not Found - GET https://registry.npmjs.org/@modelcontextprotocol%2fclient-cli - Not found

(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 since 82484ff (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-remote as the command, so the reader ends up with a config pointing at a binary the documented install can never provide. Running your own connector on a5438ee (Python 3.12):

connect_ide('cursor', home=<tmp>, transport='http-mcp-remote')
{"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"), and slm connect --transport http-mcp-remote is a documented flag (cli/main.py).

What it is now

The same three lines name mcp-remote — the package that actually ships that binary:

$ npm install -g --prefix ./pfx mcp-remote
added 81 packages in 2s
$ ls pfx/bin
mcp-remote -> ../lib/node_modules/mcp-remote/dist/proxy.js
mcp-remote-client -> ../lib/node_modules/mcp-remote/dist/client.js
$ pfx/bin/mcp-remote
Usage: npx tsx proxy.ts <https://server-url> [callback-port] [--debug]

(mcp-remote 0.1.38 — the binary name matches the command your connector writes.)

Checks

tests/test_cli_subparsers/test_transport_connect.py on this branch: 15 passed (Python 3.12). Identical result on unmodified main — 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.

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)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants