Workstation WSL Proxy: API Gateway, CDN & Agent Edge

Workstation WSL Proxy (WSLProxy) is Workstation’s open API gateway and CDN edge control plane — live routing, WAF, cache, multi-POP DNS, and MCP for agents. Product page: /wsl-proxy. Deep dive: long article.

What it is

WSLProxy is a dynamic API gateway and reverse proxy on OpenResty. Operators manage virtual hosts, rules, WAF, cache, traffic splits, and edge POPs from an Admin UI, REST API, MCP tools, or wslproxy-cli. It is built for multi-POP edges, GitOps-style config, and AI agents — the same stack that fronts workstation.co.uk traffic in production patterns.

Complete API gateway + CDN

• Routing: path / IP / country / JWT / cookie match → proxy, redirect, HTML, CAPTCHA.
• Traffic: weighted, RR, canary, sticky, least-conn; promote and rollback backends.
• WAF: policy packs, anomaly scoring, monitor/block, events API.
• CDN cache: edge static cache, optional Docker blob cache, Varnish hooks.
• POPs + DNS: declare edges; Cloudflare A-record provisioning with guardrails.
• Control plane: React Admin, Swagger, MCP (Claude/Cursor), CLI image on GHCR.

Agents Gateway & MCP Gateway (roadmap)

Workstation is extending the same edge into the agent era:

• MCP Gateway (in progress): governed front door for external MCP servers — auth bridging, tool allow/deny, audit of tools/call, per-tool rate limits.
• Agents Gateway (in progress): policy and observability for multi-agent traffic through the Workstation WSL Proxy edge.
• MCP management (available now): drive WSLProxy’s own Admin surface from Claude/Cursor via MCP tools.

Where to start

1. Open wslproxy.org and the Swagger API.
2. Clone github.com/bwalia/wslproxy and run Compose or Helm for k3s.
3. Read the technical article or the product page.

Published by Workstation.

Product site: https://wslproxy.com/