Guide: connect your proxies to your AI (MCP)

The ProxySEO MCP connector (Model Context Protocol) lets your AI assistant —Claude Desktop, Claude Code, Codex, Cursor, LangChain…— use your dedicated proxies directly: list your IPs, get a ready-to-use proxy or check that it works, all from the conversation. Setup takes about 5 minutes.

Just the essentials? 1) generate your API key in the panel, 2) download the connector, 3) paste the config into your AI client, 4) restart it. Details below.

1Generate your API key

Go to your client area → your proxy service → the "AI agent access (MCP)" card → "Generate API key" button.

Important: the key is shown only once. Copy it and store it in a password manager. If you lose it, revoke it and generate a new one (up to 3 active keys).

2Download the connector

Pick the binary for your operating system from the latest release:

System	File
Windows	proxy-mcp-windows-amd64.exe
macOS (Apple Silicon · M1/M2/M3)	proxy-mcp-darwin-arm64
macOS (Intel)	proxy-mcp-darwin-amd64
Linux (64-bit)	proxy-mcp-linux-amd64
Linux (ARM64)	proxy-mcp-linux-arm64

3Install the connector

macOS

Linux

Windows

Open Terminal and, from your Downloads folder, make it executable and move it into your PATH (adjust the filename for your Mac):

chmod +x ~/Downloads/proxy-mcp-darwin-arm64
sudo mv ~/Downloads/proxy-mcp-darwin-arm64 /usr/local/bin/proxy-mcp

The first time, macOS may block it for security. If so: System Settings → Privacy & Security → "Open Anyway", or run:

xattr -d com.apple.quarantine /usr/local/bin/proxy-mcp

chmod +x ~/Downloads/proxy-mcp-linux-amd64
sudo mv ~/Downloads/proxy-mcp-linux-amd64 /usr/local/bin/proxy-mcp

Create a folder, e.g. C:\Tools\proxyseo\, and move the downloaded file there. Rename it to proxy-mcp.exe for simplicity. The full path will be C:\Tools\proxyseo\proxy-mcp.exe (you'll need it in step 4).

In the Windows config, use double backslashes in the path: C:\\Tools\\proxyseo\\proxy-mcp.exe

4Configure your AI client

Replace TU_API_KEY with the key from step 1 and, on Windows, the command path with the one from step 3.

Claude Desktop

Claude Code

Cursor / others

Open Claude Desktop → Settings → Developer → Edit Config. That opens claude_desktop_config.json:

macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json

Add the proxyseo block inside mcpServers:

{
  "mcpServers": {
    "proxyseo": {
      "command": "/usr/local/bin/proxy-mcp",
      "env": {
        "PROXYSEO_API_KEY": "TU_API_KEY"
      }
    }
  }
}

From the terminal, in your project:

claude mcp add proxyseo /usr/local/bin/proxy-mcp \
  --env PROXYSEO_API_KEY=TU_API_KEY

Or manually add the same mcpServers block to .mcp.json at your project root, as in Claude Desktop.

Cursor and most MCP-compatible clients use the same format. In Cursor: Settings → MCP → Add new server, or edit ~/.cursor/mcp.json:

{
  "mcpServers": {
    "proxyseo": {
      "command": "/usr/local/bin/proxy-mcp",
      "env": {
        "PROXYSEO_API_KEY": "TU_API_KEY"
      }
    }
  }
}

Any MCP client that accepts a stdio command works: LangChain, Codex, your own agents, etc.

5Restart and test

Fully quit and reopen your AI client. Then try a prompt like:

List my ProxySEO proxies and check they work.

If everything is set up, your AI will use the connector tools and return your IPs and their status.

Available tools

Tool	What it does
list_proxies	Lists all your service IPs in IP:port format.
get_proxy	Returns a ready-to-use proxy (connection URL or JSON with credentials).
proxy_status	Service status: plan, auth type, number of IPs and ports.
check_proxy	Checks in real time that the proxy reaches the internet and is anonymous.

Troubleshooting

The server doesn't show up in my AI client

Fully restart it (not just the window). Check that the command path is correct and the file is executable (step 3).

Authentication error / 401

The API key is wrong or was revoked. Generate a new one in the panel and update your config.

macOS says it can't verify the developer

Run the xattr command from step 3, or allow it under Settings → Privacy & Security.

check_proxy fails

Wait 1–2 minutes after the service is activated (IPs take a moment to propagate) and retry. If it persists, open a ticket.

Need help? Open a ticket from your client area and we'll help you out.