$
Sign inSign up

Prokso MCP server in Zed

Zed supports remote MCP servers: you set the address and headers in the settings, so the Prokso API key is sent the same way as in the REST API, in the Authorization header.

1. What you need

  • Zed with the Agent Panel. The Zed docs do not name a minimum version for remote servers, so update the editor to a recent version.
  • A Prokso API key. Create it in the dashboard under "Settings" → "API". The full key is shown only once.

The list of tools and what they return is on the Prokso MCP server page.

2. The context_servers block

Open Settings → AI → MCP Servers or run the zed: open settings file action and add:

{
  "context_servers": {
    "prokso": {
      "url": "https://prokso.com/api/v1/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}

If the file already has other settings, paste only the context_servers block inside the existing curly braces. The name prokso is up to you: it labels the server in the list and in permission rules.

The Authorization header is required. Without it Zed offers an OAuth sign-in, and our server has no OAuth: sign-in is by key only. The Zed docs do not describe environment variable substitution in headers, so the key goes in as plain text.

3. How to check

  1. Open Settings → AI → MCP Servers: next to prokso there should be a green dot with the tooltip "Server is active". Any other color means a problem, and the tooltip says which.
  2. In the Agent Panel, type: "Use prokso to show my balance". Naming the server nudges the agent to use its tools: get_account, get_prices, list_plans, get_plan, get_proxy_lines.
  3. By default Zed asks for permission before every tool call (agent.tool_permissions.default set to "confirm"). You can allow single tools with rules like mcp:prokso:list_plans.

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 host and ports of plan 12 and write a connection example for requests in Python."
  • "Give me 20 lines with a new IP on every request from the US, state of Texas, for plan 12."

The last prompt uses precise geo: such traffic counts double, and we do not guarantee addresses in a specific state or city. All ports and parameters are in the gateway reference. The tools only read data; buying is done in the dashboard or via the REST API.

5. If it does not work

  • Zed opens a sign-in in the browser: the header was not applied. Check the nesting: headers must sit inside prokso, next to url.
  • 401 means the key is wrong or revoked; check that there is exactly one space after Bearer.
  • 429 means more than 60 requests per minute with one key. Wait as many seconds as the Retry-After header says.

Check the server outside the editor; the response should list 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 server errors are on the MCP server page.

6. Keeping the key safe

  • The key sits in the settings file as plain text. The file is personal, but if you keep your settings in git (dotfiles), the key ends up there: move the block out or exclude the file.
  • Create a separate key for Zed (up to 5 per account), so you can revoke just that one.
  • If the key may have leaked, revoke it under "Settings" → "API" and create a new one.

Proxy setup in apps is in Guides, and line diagnostics are step by step.

MCP in Cline →How to use Prokso