Skip to content

docs: switch mcp-bridge invocation from node to deno run -A#45

Merged
hyperpolymath merged 1 commit intomainfrom
docs-node-to-deno-2026-05-01
May 2, 2026
Merged

docs: switch mcp-bridge invocation from node to deno run -A#45
hyperpolymath merged 1 commit intomainfrom
docs-node-to-deno-2026-05-01

Conversation

@hyperpolymath
Copy link
Copy Markdown
Owner

Summary

mcp-bridge/main.js is a Deno program (uses Deno.env.get, Deno.stdin.readable, Deno.exit — confirmed via grep; ships mcp-bridge/deno.json with Deno task config). Several user-facing docs and package.json's "start" script told users to launch it with node, producing ReferenceError: Deno is not defined on first install.

This came from a 2026-04-30 install session where the maintainer hit that exact error running claude mcp add ... -- node ... mcp-bridge/main.js per the README.

Premise verification: grep -n 'Deno\.' mcp-bridge/main.js returns lines 249, 496, 507 — confirmed Deno API usage. mcp-bridge/deno.json exists with deno run --allow-net --allow-env --allow-read main.js as its start task.


Files changed

File Lines changed Rationale
package.json 1 scripts.start used node mcp-bridge/main.js; changed to deno run -A mcp-bridge/main.js so npm start works
README.md 1 Clone-and-configure snippet instructed claude mcp add boj-server -- node mcp-bridge/main.js
README.adoc 2 Two install snippets: one with absolute path (node /path/to/…), one relative (node mcp-bridge/main.js)
docs/index.html 1 Landing-page install snippet had node /path/to/boj-server/mcp-bridge/main.js

Total: 4 files, 5 lines changed (5 substitutions).


Deliberately left alone

Item Reason
mcp-bridge/main.js Source is already correct Deno — no change needed
package.jsonbin.boj-server npx/npm-publish story for a Deno bridge needs its own decision; out of scope for this PR
package.jsonscripts.test (node --test …) Runs the Node test runner against dispatch_test.js; separate from bridge invocation
README.adoc line 107 (node --test mcp-bridge/tests/) Same — test-runner invocation, not bridge launch
package.jsonengines.node One-line cleanup per request scope; engines block left as-is
docs/practice/DOGFOOD-LOG.adoc line 149 Historical incident log recording a past /usr/bin/node bug; editing a log entry would falsify the record
All workflow / cartridge / service files Explicitly out of scope

How to test

git clone https://github.com/hyperpolymath/boj-server
cd boj-server/mcp-bridge
# Start the BoJ REST API first (port 7700), then:
claude mcp add boj-server -- deno run -A mcp-bridge/main.js

No more ReferenceError: Deno is not defined.


Generated by Claude Code

mcp-bridge/main.js uses Deno APIs (Deno.env.get, Deno.stdin.readable,
Deno.exit) and ships a deno.json config, but README.md, README.adoc,
docs/index.html, and package.json#start all told users to launch it with
node, causing ReferenceError: Deno is not defined on first install.

https://claude.ai/code/session_01G9pKozzr5GYMkAC9NgqUju
@hyperpolymath hyperpolymath merged commit 95ec8aa into main May 2, 2026
9 of 13 checks passed
@hyperpolymath hyperpolymath deleted the docs-node-to-deno-2026-05-01 branch May 2, 2026 18:50
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