Prokso MCP server in Claude Desktop and claude.ai

1. What you need and which way to choose

• A Prokso API key: dashboard, "Settings" > "API" > "Create key". Test it with curl as shown on the "Prokso MCP server" page.
• Way 1: a connector with a request header. Works in both Claude Desktop and claude.ai. The Request headers section of the add-connector dialog is a beta feature available to a limited set of organizations. If you don't see it, go to way 2.
• Way 2: the mcp-remote bridge. Claude Desktop app only. You need Node.js 18 or newer: the bridge runs on your computer and forwards requests to the Prokso server with your header.

This guide follows the Claude connectors help and the mcp-remote package README as of November 2026. Menu names are given as they appear in the Claude interface.

2. Way 1: a connector with a header

1. Open Customize → Connectors and click Add custom connector.
2. In the server URL field, enter https://prokso.com/api/v1/mcp.
3. For authentication, choose No sign-in: the key goes in a header, no OAuth is needed.
4. Open Request headers, pick the authorization name and enter the value Bearer YOUR_API_KEY exactly like that, with the word Bearer and a space: Claude sends the value as is. Mark the header as Required.
5. Click Add.

You can't change the header after saving: to use a new key, remove the connector and add it again. On Team and Enterprise plans an Owner adds the connector, and the header is then shared by all members, so everyone sees the plans of one Prokso account. For a personal key, way 2 or Claude Code is a better fit.

3. Way 2: the mcp-remote bridge in Claude Desktop

In Claude Desktop, open the Claude → Settings menu (the app menu, not your account settings), go to the Developer tab and click Edit Config. This opens the config file:

Add the Prokso server (if the file already has other servers, put the prokso block inside mcpServers):

{
  "mcpServers": {
    "prokso": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://prokso.com/api/v1/mcp",
        "--transport",
        "http-only",
        "--header",
        "Authorization:${AUTH_HEADER}"
      ],
      "env": {
        "AUTH_HEADER": "Bearer YOUR_API_KEY"
      }
    }
  }
}

The key goes into the AUTH_HEADER variable, and the argument has no space after the colon. The mcp-remote README recommends this because Claude Desktop on Windows doesn't pass spaces inside args correctly. The --transport http-only option tells the bridge not to try the older SSE transport. Save the file, quit Claude Desktop completely and start it again.

4. Check it

In the message box, click the + button ("Add files, connectors, and more"), hover over Connectors and open Manage connectors. Pick prokso: you should see five tools, get_account, get_prices, list_plans, get_plan, get_proxy_lines. The same menu turns the connector on or off for a single chat.

First requests:

• "How much traffic is left on my Prokso plans?"
• "Give me 5 SOCKS5 lines with fixed IPs in Poland for plan 12."
• "Show the host and ports of my plan and explain what each port is for."

Claude asks for permission before calling a tool. Use "Always allow" only when you're sure about the setup.

5. If it doesn't work

• No Request headers section: your organization doesn't have the beta yet. Use way 2 or Claude Code.
• The connector asks you to sign in or shows an authentication error: OAuth sign-in was chosen, or the header lacks Bearer. Remove the connector and add it again with No sign-in.
• The server from way 2 doesn't appear: check the JSON syntax, Node.js 18+ (node --version) and the logs: on macOS tail -n 20 -f ~/Library/Logs/Claude/mcp*.log, on Windows the %APPDATA%\Claude\logs folder.
• 401 in the log: the key is wrong or revoked. 429: the limit of 60 requests per minute is exceeded.

Other errors are on the MCP server page, proxy problems in the step-by-step check.

6. Key security

In way 2 the key sits in claude_desktop_config.json in plain text: don't share this file or sync it to public places. In way 1 Claude stores the header value and never shows it again. Create a separate key for Claude and revoke it in "Settings" > "API" if in doubt. The agent can't buy traffic over MCP; use the dashboard or the REST API for that. Proxy setup in apps is in the "Guides" section, ports in the gateway reference.

MCP in Cursor →How to use Prokso