reverse-bridge

Exposes a local repository to a MySpec brownfield spec session over a reverse WebSocket MCP bridge.

Updated Sep 12, 2026
One-click install
npx skills add https://github.com/myspecs/claude-plugins --skill reverse-bridge-myspecs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: reverse-bridge
Source: https://github.com/myspecs/claude-plugins/tree/main/plugins/myspec-mcp/skills/reverse-bridge
Command: npx skills add https://github.com/myspecs/claude-plugins --skill reverse-bridge-myspecs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires @myspec/mcp-server.

What problem does it solve? When drafting a brownfield spec in the MySpec webapp, the cloud AI agent cannot read your existing local codebase. This Skill runs the MySpec reverse MCP bridge, which dials out from your machine over WebSocket and grants the cloud agent read-only access to one local directory without opening any inbound connections. ## Core Features & Use Cases - Reverse MCP Bridge: Starts a long-running process via npx -y @myspec/mcp-server reverse --root <dir> that exposes read-only filesystem tools (list, read, grep, repomix codebase packing) confined to the chosen root. - Readiness & Health Checks: Polls the reverse-mcp status endpoint with curl and jq to confirm the bridge is connected before continuing in the webapp. - Troubleshooting Guidance: Resolves common failures such as missing active organization, HTTP 401 WebSocket rejections, account mismatches, and close code 4002 evictions. - Use Case: You are writing a brownfield spec in the MySpec webapp and the session reports reverse_mcp_unavailable. Use this Skill to start the bridge against your repo root, verify the connection, and let the cloud agent read your code. ## Quick Start Ask the assistant to share your local repository with MySpec by starting the reverse bridge rooted at your project's absolute path, then confirm it reports connected before continuing in the webapp.

Frequently Asked Questions about reverse-bridge

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I share my local code with a MySpec brownfield spec session?▼

Run `npx -y @myspec/mcp-server reverse --root /absolute/path/to/repo` in a separate terminal after signing in. The CLI dials out over WebSocket and exposes read-only filesystem tools scoped to that directory for the cloud agent.

What tools does the MySpec reverse bridge expose to the cloud agent?▼

The bridge exposes read-only tools confined to the root: local_fs_list_dir, local_fs_read_file (5 MiB per file, 2000 lines per call), local_fs_grep, and local_pack_codebase for paginated repomix XML packs. Absolute paths and `..` are rejected.

Why does the MySpec webapp session report reverse_mcp_unavailable?▼

This usually means the bridge registration has not finished right after startup, or no bridge is running for your account. Start the reverse command, then poll the reverse-mcp status endpoint until it returns connected:true before retrying in the webapp.

Can the MySpec reverse bridge write to or modify my local files?▼

No. The bridge only exposes read-only tools such as directory listing, file reading, grep, and codebase packing, all confined to the directory passed via --root. Nothing outside that root is reachable and no inbound connections reach your machine.

Why does the reverse bridge disconnect with WebSocket close code 4002?▼

Close code 4002 means another reverse bridge for the same MySpec account connected elsewhere, and only one live bridge is allowed per account. Stop the other instance or accept that the newest connection wins.

How do I run the MySpec reverse bridge on a headless machine without a browser?▼

Run `login --paste` and open the printed URL on any machine with a browser to complete sign-in, since reverse requires a real session matching the browser account. Do not copy ~/.myspec/ between machines because refresh tokens are single-use.