Skip to content

t1k:cocos:omarchy:editor-bridge

FieldValue
Moduleomarchy
Version0.4.2
Effortmedium
ToolsAskUserQuestion, Bash, Read

Keywords: cocos mcp winpodx, cocos-creator mcp omarchy, cocos-mcp-server guest, editor bridge linux, extra_ports cocos, mcp port forward cocos

/t1k:cocos:omarchy:editor-bridge
[--dry-run]

The cocos-mcp-server extension runs inside the Creator window in the guest and binds the guest’s 127.0.0.1:<port>. A client on the Linux host dialing 127.0.0.1:<port> reaches the host loopback, so without plumbing the connection is refused.

Chain this module builds (config only, no secrets): host 127.0.0.1:P -> winpodx pod.extra_ports (127.0.0.1:P:P+offset/tcp, merged with your own forwards) -> guest netsh portproxy 0.0.0.0:P+offset -> 127.0.0.1:P + a firewall rule.

  1. Read each project’s port: bun .claude/skills/t1k-cocos-base-editor-mcp-truth/scripts/resolve-mcp-port.cjs <project> --json; put them in bridge.ports (ports differ per project; the extension default is 3000).
  2. bun $S apply --only bridge (S = winpodx skill script). The guest step needs a running, elevated guest; otherwise it reports needs-you: run the printed portproxy step as Administrator in the guest, then ack bridge:guest-portproxy.
  3. Pod-level change: winpodx pod recreate (handoff) so the compose forward exists.
  4. Start the cocos-mcp-server panel in Creator (handoff). The extension generates its own authToken in <project>/settings/mcp-server.json; register the client with base’s register-mcp-auth.cjs - it reads the token at run time. This module never reads, prints or writes that token, and never writes .mcp.json.
  5. bun $S doctor --project <project> - the final health proof is base’s editor-doctor.cjs.

Not checkable without a guest: the portproxy script and that QEMU’s forward reaches the proxy port.