Skip to content

AgentDock BridgePersonal Remote MCP Bridge

Authenticates remote MCP clients via Cloudflare Workers OAuth 2.1 + PKCE, requires exact manual approval on a hardened Windows host, and executes workspace tools in a read-only Linux Docker container.

AI Translation Notice

English documentation pages are translated/synchronized from the authoritative Chinese source (简体中文首页) using inspected repository facts. Refer to the Chinese pages or source files if any subtle phrasing differs.

Capabilities & Explicit Limits ​

What AgentDock Bridge Delivers

  • Authenticated Edge OAuth 2.1 & Outbound WSS: Separates AuthCoordinator and BridgeRelay SQLite DOs and dials out over WSS /bridge without opening inbound ports on your router.
  • Per-Parameter Approve.cmd & Anti-Replay Ledger: Every mutating/read/exec call outside computer_context, command_status, and stop_command hashes exact arguments for manual terminal confirmation, unlinking .approved.json before recording 24h RequestReceipts.
  • 10 Hardened MCP Tools inside Disposable Linux Containers: Executes inside --read-only, --cap-drop ALL (SETUID/SETGID), UID/GID 1000, and --network none containers with expected_sha256 CAS checks and Windows DACL guards.

Explicit Non-Goals & Hard Boundaries

  • Single-Owner & Windows Host Coupling: Supports one owner and one /workspace root with zero multi-tenancy; production DPAPI (loadSecrets) and NTFS ACL checks require Windows x64 (win32).
  • Not Blind E2E Encryption: Cloudflare edge nodes and your upstream AI client platform still observe /mcp arguments and outputs, and approved tools intentionally read files inside /workspace.
  • Strict Payload Caps & Cleanup Lockout: Uses POST /mcp JSON-RPC 2.0 (no SSE streams) capped at 1 MiB ingress / 2 MiB reply / 110s deadline; unconfirmed docker rm -f halts new tasks until reset.

Architecture Overview ​

AgentDock Bridge Topology (pan / zoom / inspect supported)
Open Fullscreen ↗

Implementation Note: The diagram visualizes the four high-level zones from client gateway to sandbox. In actual source code, client RPC uses HTTP POST /mcp (JSON-RPC 2.0 rather than SSE log streams), OAuth 2.1 + PKCE (S256), outbound connector WebSocket WSS /bridge, and per-invocation docker start --attach after Approve.cmd.

Verification & Client Endpoint Quick Check ​

Run static syntax checks and cross-platform tests with Node.js 24+ and pnpm@12.6.0 (15 Windows/Docker-specific tests skip automatically on non-Windows/no-Docker hosts):

sh
pnpm install --frozen-lockfile
pnpm run check
pnpm test

Configure compatible remote MCP clients with your deployed PUBLIC_ORIGIN endpoint:

text
https://<your-bridge-domain>/mcp

Documentation Guide ​

Quick Navigation by Role & Goal