Prokso MCP server in VS Code

1. What you need

• VS Code with GitHub Copilot and chat in agent mode. The VS Code docs do not name a minimum version: if there are no MCP: commands in the palette, update the editor.
• A Prokso API key. Create it in the dashboard under "Settings" → "API". The full key is shown only once, so copy it right away.
• A project folder open in VS Code.

What the server can do and what each tool returns is on the Prokso MCP server page.

2. The .vscode/mcp.json file

Create .vscode/mcp.json in the project root (the MCP: Open Workspace Folder MCP Configuration command opens it too) and paste:

{
  "inputs": [
    {
      "type": "promptString",
      "id": "prokso-key",
      "description": "Prokso API key",
      "password": true
    }
  ],
  "servers": {
    "prokso": {
      "type": "http",
      "url": "https://prokso.com/api/v1/mcp",
      "headers": {
        "Authorization": "Bearer ${input:prokso-key}"
      }
    }
  }
}

• servers is the list of servers; type: "http" means a remote server at url.
• inputs is a field VS Code shows when the server starts for the first time. With password: true the input is masked, and the editor keeps the value in secure storage.
• ${input:prokso-key} in the Authorization header inserts the key you entered.

You can add the same block to your personal file with MCP: Open User Configuration; the server is then available in every project.

3. How to check

1. Run MCP: List Servers, pick prokso and start the server. VS Code asks for the key; paste it. If the editor asks whether you trust the server, confirm.
2. In chat, in agent mode, open the tool picker (Configure Tools): the prokso group should list five tools: get_account, get_prices, list_plans, get_plan, get_proxy_lines.
3. Type in chat: "Use prokso to show my balance". Expand the tool call in the conversation: it should be get_account with a response and no error.

4. Example prompts

• "How much traffic is left on my plans?"
• "Give me 5 SOCKS5 lines with sticky IPs in Poland for plan 12."
• "Show the username, host and ports of plan 12."
• "Generate 10 HTTP lines with a new IP on every request in host:port:username:password format and save them to proxies.txt."

The tools only read data: the agent cannot buy traffic or change a plan. Ports and geo parameters in the lines work as described in the gateway reference; precise geo (state, city, carrier) counts traffic double, and we do not guarantee that a specific city is available.

5. If it does not work

• 401 in the server log means the key is wrong or revoked. VS Code remembers the value you entered, so change the id in inputs and in ${input:…} (for example to prokso-key-2) and restart the server; the editor will ask for the key again.
• 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 start, or the log mentions SSE. VS Code tries HTTP first and falls back to SSE only after that. Our server works without SSE, so such an attempt means the first POST request failed: check the address and the key. Open the log from MCP: List Servers → prokso → Show Output.

Check the key outside the editor; the response should contain a list of 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"}'

Other error codes are on the MCP server page, and the same actions from code are in the API docs.

6. Keeping the key safe

The key gives access to the proxy lines of your account, so:

• do not put the key straight into mcp.json: the .vscode folder often ends up in git, and the inputs field keeps the key out of the file;
• create a separate key for each editor or computer (up to 5 per account), so you can revoke one without touching the others;
• if the key may have leaked, revoke it under "Settings" → "API" and create a new one.

Proxy setup in apps and browsers is in Guides, and checking the proxy itself is step by step.

MCP in Windsurf →How to use Prokso