
Proxy Doctor
This is for the specific hell of when your browser loads fine but Cursor or VS Code's AI features won't connect. It checks five layers on macOS: system proxy settings via networksetup, stale localhost ports from closed VPN apps, lingering launchctl environment variables, editor configs in settings.json, and whether proxy ports actually have something listening. The MCP server exposes diagnose_proxy, list_fixes, and supported_editors tools that return structured JSON with root cause analysis and executable networksetup commands. Built for the common case where a proxy was disabled but left 127.0.0.1:10903 configured somewhere, breaking streaming connections that AI completions depend on.
- GitHub stars
- 1
- tools
- 3
- transport
- STDIO
- last updated
- Feb 28, 2026
Tools
3 toolsPublic tool metadata for what this MCP can expose to an agent.
diagnose_proxyFull 5-layer diagnosis with evidence.
Full 5-layer diagnosis with evidence.
No parameter schema in public metadata yet.
list_fixesRecommended fixes with executable commands.
Recommended fixes with executable commands.
No parameter schema in public metadata yet.
supported_editorsList available editors.
List available editors.
No parameter schema in public metadata yet.
Sponsors
Readme
proxy-doctor logo
proxy-doctor
Diagnose proxy misconfigurations that break AI coding tools.
When your browser works fine but Cursor / VS Code / Windsurf AI features don't — proxy-doctor tells you exactly why and how to fix it.
The Problem
AI coding tools (Cursor, VS Code with Copilot, Windsurf) rely on long-lived streaming connections (SSE/HTTP2) that break when:
Details
- Repository
- github.com/jiansen/proxy-doctor
- Package
proxy-doctor- Transport
- STDIO
- Registry
- MCP registry, active