Diagnose proxy misconfigurations that break AI coding tools (Cursor, VS Code, Windsurf)
{
"mcpServers": {
"io-github-jiansen-proxy-doctor": {
"command": "<see-readme>",
"args": []
}
}
}No install config available. Check the server's README for setup instructions.
Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Diagnose proxy misconfigurations that break AI coding tools (Cursor, VS Code, Windsurf)
Is it safe?
No package registry to scan.
No authentication — any process on your machine can connect.
License not specified.
Is it maintained?
Last commit 39 days ago.
Will it work with my client?
Transport: stdio. Works with Claude Desktop, Cursor, Claude Code, and most MCP clients.
No automated test available for this server. Check the GitHub README for setup instructions.
No known vulnerabilities.
This server is missing a description. Tools and install config are also missing.If you've used it, help the community.
Add informationHave you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Persistent memory using a knowledge graph
Privacy-first. MCP is the protocol for tool access. We're the virtualization layer for context.
Pre-build reality check. Scans GitHub, HN, npm, PyPI, Product Hunt — returns 0-100 signal.
Monitor browser logs directly from Cursor and other MCP compatible IDEs.
MCP Security Weekly
Get CVE alerts and security updates for io.github.Jiansen/proxy-doctor and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
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.
AI coding tools (Cursor, VS Code with Copilot, Windsurf) rely on long-lived streaming connections (SSE/HTTP2) that break when:
launchctlThe result: "browser works, AI editor doesn't" — the most common and frustrating developer experience.
proxy-doctor inspects 5 layers of your macOS proxy configuration:
| Layer | What | How |
|-------|------|-----|
| 1. System Proxy | Web/HTTPS/SOCKS proxy across all network services | networksetup |
| 2. Residual Values | Disabled proxies with stale localhost addresses | Parse disabled-but-set entries |
| 3. Port Health | Whether referenced proxy ports are actually listening | socket.connect() |
| 4. Editor Config | settings.json, argv.json, recent error logs | File read + pattern match |
| 5. GUI Environment | http_proxy/https_proxy in GUI app context | launchctl getenv |
# Install
pip install proxy-doctor
# Run diagnosis (JSON output — default, optimized for AI agents)
proxy-doctor check
# Run diagnosis (human-readable output)
proxy-doctor check --human
# Show recommended fixes
proxy-doctor fix
# Check a different editor
proxy-doctor check --editor vscode
proxy-doctor ships as an MCP server that AI agents can call directly:
# Install with MCP support
pip install proxy-doctor[mcp]
# Run MCP server
python -m proxy_doctor.mcp_server
Add to your MCP configuration (e.g., Cursor ~/.cursor/mcp.json):
{
"mcpServers": {
"proxy-doctor": {
"command": "python3",
"args": ["-m", "proxy_doctor.mcp_server"]
}
}
}
Note:
"command"must point to the Python whereproxy-doctor[mcp]is installed. Ifpython3doesn't work, use the full path (runwhich python3orpython3 -c "import sys; print(sys.executable)"to find it).
Your AI agent can then call:
diagnose_proxy(editor="cursor") — full 5-layer diagnosis with evidencelist_fixes(editor="cursor") — recommended fixes with executable commandssupported_editors() — list available editorsOne-liner (paste this to your AI agent):
Install proxy-doctor (
pip install proxy-doctor[mcp]) and add it to your MCP config with commandpython -m proxy_doctor.mcp_server. Then use thediagnose_proxytool to check proxy health.
If you are an AI agent setting up proxy-doctor for your user:
# 1. Install
pip install proxy-doctor[mcp]
# 2. Find the Python path
python3 -c "import sys; print(sys.executable)"
# 3. Add to ~/.cursor/mcp.json (use the path from step 2)
# {
# "mcpServers": {
# "proxy-doctor": {
# "command": "<python-path-from-step-2>",
# "args": ["-m", "proxy_doctor.mcp_server"]
# }
# }
# }
... [View full README on GitHub](https://github.com/Jiansen/proxy-doctor#readme)