Prokso MCP server in Windsurf

1. What you need

• Windsurf with the Cascade panel.
• A Prokso API key. Create it in the dashboard under "Settings" → "API". The full key is shown only once.
• Access to your home folder, where the MCP settings file lives.

The paths and field names below follow the Windsurf docs as of 02.11.2026. The English version of that page now redirects to the Devin Desktop docs, so menu items may be named differently in newer builds. What the server itself can do is on the Prokso MCP server page.

2. The mcp_config.json file

Open the MCP settings: the MCPs icon in the top right of the Cascade panel, or Windsurf Settings → Cascade → MCP Servers. A custom server is added by hand to the raw file ~/.codeium/windsurf/mcp_config.json:

{
  "mcpServers": {
    "prokso": {
      "serverUrl": "https://prokso.com/api/v1/mcp",
      "headers": {
        "Authorization": "Bearer ${env:PROKSO_API_KEY}"
      }
    }
  }
}

A remote server is set with the serverUrl field (Windsurf also accepts url) instead of command. Windsurf replaces ${env:PROKSO_API_KEY} with the value of the environment variable: this works in the serverUrl, url and headers fields. Set the variable and restart the editor:

# macOS, Linux
export PROKSO_API_KEY=YOUR_API_KEY

# Windows
setx PROKSO_API_KEY YOUR_API_KEY

On macOS and Linux the variable is visible to apps started from the same terminal, so open Windsurf from there. You can also put the key in directly, "Bearer YOUR_API_KEY": the file sits in your home folder, not in the project, but then anyone who opens the file can read the key.

3. How to check

1. Save the file and refresh the server list in the MCP panel with the refresh button.
2. prokso appears in the list with five tools: get_account, get_prices, list_plans, get_plan, get_proxy_lines. Cascade can see up to 100 tools at a time, so if you have many servers, turn off the ones you do not need.
3. Type in Cascade: "Use prokso to show my balance". The agent should call get_account and show your email and balance.

4. Example prompts

• "How much traffic is left on my plans?"
• "Give me 5 SOCKS5 lines with sticky IPs in Poland for plan 12."
• "What are the current prices per GB?"
• "Give me 3 HTTP lines from Germany for plan 12 in the format with the protocol and add them to my scraper config."

The tools only read data and return lines: they never spend money, and buying is done in the dashboard or via the REST API. Ports and geo parameters work as in the gateway reference; precise geo counts traffic double.

5. If it does not work

• 401 means the key is wrong or revoked, or the variable did not reach the editor and an empty Bearer was sent. Check the variable in the environment Windsurf was started from.
• 429 means more than 60 requests per minute with one key. Wait as many seconds as the Retry-After header says.
• The server does not appear: check the JSON (one extra or missing comma breaks the whole file) and the address, /api/v1/mcp with no trailing slash.

You can see whether the key works without the editor; the response lists five tools:

curl -X POST https://prokso.com/api/v1/mcp -H "Authorization: Bearer YOUR_API_KEY" -H "Content-Type: application/json" -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

Server error codes are described on the MCP server page.

6. Keeping the key safe

• The key gives access to the proxy lines of your account: keep it in an environment variable and do not copy mcp_config.json with the key into a repository.
• Create a separate key for Windsurf (up to 5 per account), so you can revoke it without breaking other integrations.
• If the key may have leaked, revoke it under "Settings" → "API".

How to set up proxies in the apps themselves is in Guides; if the lines from the agent do not work, use the step-by-step check.

MCP in Zed →How to use Prokso