Proxy Doctor MCP Server

Diagnose proxy misconfigurations that break AI coding tools (Cursor, VS Code, Windsurf)

Local serverstdioPython

What is the Proxy Doctor MCP server?

Most monitoring and observability work still happens through a UI a human drives. Proxy Doctor MCP server moves it into the conversation instead. Diagnose proxy misconfigurations that break AI coding tools (Cursor, VS Code, Windsurf).

The short version

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.

Getting it running

Installation goes through your MCP client rather than a global install: point it at proxy-doctor on PyPI and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.

The tools it exposes

The server publishes 13 tools. What each one is for:

  • macOS — Full support (system proxy, launchctl, networksetup)
  • Linux — Partial (editor config + environment variables; no networksetup)
  • Windows — Not yet supported
  • Layer — What
  • Editor — Config Detection
  • Cursor — yes
  • Windsurf — yes
  • Zed — planned
  • Access — What
  • Reads — System proxy settings, editor config files, launchctl env vars, local port status
  • Writes — ~/.proxy-doctor/ only (cache, logs, update state)
  • Network — pypi.org (version check only)

Things to watch

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • With 13 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Proxy Doctor.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

How it compares

Among the monitoring and observability options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Proxy Doctor's toolset — macOS, Linux, Windows and 10 more — is a fair guide to whether it matches your workflow. It is maintained by Jiansen; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Proxy Doctor's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Available tools

ToolWhat it does
macOSFull support (system proxy, launchctl, networksetup)
LinuxPartial (editor config + environment variables; no networksetup)
WindowsNot yet supported
LayerWhat
EditorConfig Detection
Cursoryes
Windsurfyes
Zedplanned
AccessWhat
ReadsSystem proxy settings, editor config files, launchctl env vars, local port status
Writes~/.proxy-doctor/ only (cache, logs, update state)
Networkpypi.org (version check only)
HealthyThe Healthy tool exposed by this server.

How to install the Proxy Doctor MCP server

{
  "mcpServers": {
    "proxy-doctor": {
      "command": "uvx",
      "args": ["proxy-doctor"]
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Example prompts to try

  • Use Proxy Doctor to macOS.
  • Use Proxy Doctor to Linux.
  • Use Proxy Doctor to Windows.

Frequently asked questions

It connects Proxy Doctor to MCP-compatible AI assistants such as Claude and Cursor, exposing 13 tools (macOS, Linux, Windows, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Proxy Doctor directly.