remote-browser-mcp
Use when wiring remote Hermes to a local Mac browser MCP.
- License 许可
- MIT
- 最近更新
- 2026-09-14
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- remote-browser-mcp
- author
- Hermes Agent
- license
- MIT
- version
- 1.0.0
- metadata
- { "hermes": { "tags": [ "mcp", "browser", "vessel", "tailscale", "reverse-tunnel", "remote" ], "category": "software-development", "related_skills": [ "hermes-agent", "computer-use" ] } }
- platforms
- [ "linux", "macos" ]
- description
- Use when wiring remote Hermes to a local Mac browser MCP.
02 资源文件 1
- 参考文档references/vessel-tailscale.md2.3 KB
03 SKILL.md 正文
Remote browser MCP (hub Hermes → local Mac)
Connect Hermes running on a Linux hub (devbox) to a browser MCP on a Mac (Vessel, Chrome MCP, etc.) when both are on the same Tailscale tailnet.
When to use
- User says browser MCP is on
:3100/ Vessel / local machine - Hermes is on remote Linux; Mac holds the real browser
- SSH from hub → Mac fails (publickey) but Macs can dial into the hub
- Need a reliable path that does not depend on hub outbound SSH
Architecture (this fleet)
| Role | Host | Notes |
|---|---|---|
| Hermes agent | devbox (*.<REDACTED>) |
Cannot reliably SSH to Macs |
| Browser MCP | Mac (pro / coopers-macbook-pro / coopers-mac-studio) |
Vessel default port 3100 |
| Sync/SSH direction | Mac → devbox | Hub-and-spoke; Macs own sessions |
Do not default to stdio-over-SSH (ssh mac … mcp) from hub — that path dies on publickey unless keys are fixed. Prefer HTTP MCP + reverse tunnel (or Tailscale Serve).
Preferred path: reverse tunnel + HTTP MCP
1. Confirm tunnel / listener on hub
On devbox:
ss -ltnp | grep 3100
# expect: 127.0.0.1:3100 LISTEN (often no local PID → SSH -R)
Probe (expect 401 without token for Vessel):
curl -sS -m 3 -D- http://127.0.0.1:3100/mcp -o /tmp/mcp.body | head
# Vessel: HTTP 401 {"error":"Unauthorized — missing or invalid bearer <REDACTED>"}
# Wrong path: 404 Not found
If nothing listens: Mac must start the MCP and open the reverse forward:
# On Mac (MCP already on 127.0.0.1:3100)
ssh -N -o ExitOnForwardFailure=yes \
-R 127.0.0.1:3100:127.0.0.1:3100 \
cm@<REDACTED>
Durable variant: autossh -M 0 + ServerAliveInterval=30, or a LaunchAgent.
2. Get the bearer <REDACTED> (Vessel)
Token lives only on the Mac (not in mutagen git/omp sync, not in himitsu by default):
~/.config/vessel/mcp-auth.json # { "endpoint", "token", "pid", ... }
Copy to hub (from Mac):
scp ~/.config/vessel/mcp-auth.json \
cm@<REDACTED>:/var/lib/hermes/.hermes/credentials/vessel-mcp-auth.json
Or have the user paste the token. Do not invent tokens or spray guesses.
3. Register with Hermes
Hermes HTTP MCP + header auth:
# Interactive (prompts for bearer):
hermes mcp add vessel --url http://127.0.0.1:3100/mcp --auth header
hermes mcp test vessel
# In desktop session: /reload-mcp
Config shape (secret in .env, not plaintext in yaml when using CLI header auth):
mcp_servers:
vessel:
url: "http://127.0.0.1:3100/mcp"
headers:
Authorization: <REDACTED>
timeout: 180
connect_timeout: 30
Env key pattern: MCP_<SERVERNAME_UPPER>_TOKEN (see Hermes _env_key_for_server).
Helper script (if present): ~/.hermes/scripts/wire-vessel-mcp.sh — probes auth file and wires config.
4. Verify tools
After successful hermes mcp test / reload, tools appear as mcp_vessel_* (Vessel tools are often vessel_* under that prefix). Exercise a cheap read-only tool (e.g. current tab) before driving navigation.
Alternate path: Tailscale Serve (no SSH -R)
If the MCP binds only loopback on the Mac:
# Mac
tailscale serve --bg --http=3100 http://127.0.0.1:3100
Then from hub:
hermes mcp add vessel --url http://<mac-magicdns>:3100/mcp --auth header
Use MagicDNS hostnames (pro, coopers-macbook-pro, …), never LAN IPs.
Discovery checklist (do this order)
tailscale status— which Macs are online- Hub
ss/curlon127.0.0.1:3100— tunnel already up? - If closed: probe Mac:3100 over Tailscale (
nc/curlto MagicDNS) - Identify product by response body (Vessel → bearer <REDACTED>
/mcp) - Fetch token from Mac path or user
hermes mcp add+test+/reload-mcp
Pitfalls
- Hub → Mac SSH publickey denial — expected on this fleet until hub key is on Darwin
authorized_keys. Do not thrash stdio-SSH; use reverse tunnel or Serve. - MCP bound 127.0.0.1 only — Tailscale direct connect fails; tunnel or Serve required.
- Wrong path — Vessel is
/mcp(streamable HTTP), not/sseor/. - Missing bearer — 401 with Vessel’s exact JSON error; fix token, not network.
- Token not on hub —
mcp-auth.jsonis Mac-local; scp/paste every Vessel restart if token rotates. - SSH -R listener has no PID in
ss— normal for remote-forward sockets owned by sshd. - PATH stripped in agent shells — prefer absolute paths or
export PATH=/run/current-system/sw/bin:...on NixOS hub beforecurl/sspipelines. - Do not store live bearer <REDACTED> in skills or MEMORY.md — credentials dir +
.envonly.
Related
- Hermes native MCP reference: hermes-agent skill →
references/native-mcp.md - Desktop computer use (cua-driver) is a different path (stdio/SSH); see
computer-useskill - Session detail:
references/vessel-tailscale.md
04 同仓库更多 Skills
plan
Write a markdown plan to .hermes/plans/; no execution.
monorepo-fleet-sync
Sync docs and configs when a Flue monorepo fleet changes.
inspecting-hermes-desktop-dom
Read the live Hermes desktop DOM/CSS over CDP.
grounded-citations
Ground answers and documents in cited, verifiable sources.
competitor-news-monitor
Watch named companies for material news; cited digests.
blocked-page-recovery
Recover blocked/paywalled/WAF'd pages via fallbacks.