WeProxy MCP Server: Setup for Claude, Cursor and VS Code

The WeProxy MCP server is a public, read-only Model Context Protocol endpoint that lets AI assistants such as Claude, Cursor and VS Code read WeProxy products, package prices, country coverage and proxy error codes directly from the site's records. The address is https://weproxy.io/api/mcp and the transport is Streamable HTTP; no API key or account is required.

When your assistant gets a question like “Which proxy should I use to manage Instagram accounts in Turkey?” or “I'm getting a 407 error, what should I do?”, it calls this server instead of guessing. Prices and locations in the response come from the same source as the pricing page.

What is MCP?

Model Context Protocol (MCP) is an open protocol that gives AI applications a standard way to connect to external tools and data sources. An MCP server publishes a list of tools; based on the user's question, the assistant picks one of them, fills in the parameters and adds the returned structured data to its answer. The protocol is documented in detail at modelcontextprotocol.io.

The WeProxy MCP server implements this standard. The assistant you connect can read the current WeProxy catalog on every question, so it does not have to rely on outdated training data or third-party lists.

Which tools are available?

The server publishes seven tools. All of them are read-only: they do not place orders, access your account or take payments.

Most tools accept a locale parameter (tr, en, ru, de, vi). The assistant fills it in based on the conversation language, and product names and links come back in that language.

How do I add it to Claude?

In the Claude web and desktop apps, remote MCP servers are added as custom connectors:

1. In Claude, open Settings → Connectors.
2. Click Add custom connector.
3. Enter WeProxy as the name and https://weproxy.io/api/mcp as the URL, then save. No authentication is needed.
4. In a new chat, check that the connector is enabled and ask a WeProxy-related question.

How the connector option looks and whether it is available may depend on your Claude plan and organization settings. For current steps, see the Claude Help Center.

How do I add it to Claude Code?

A single command in the terminal is enough:

claude mcp add --transport http weproxy https://weproxy.io/api/mcp

Once added, run claude mcp list to confirm the server is connected. In a Claude Code session, a request such as “Get WeProxy residential proxy prices for Turkey” calls the get_pricing tool.

How do I add it to Cursor and VS Code?

Cursor: Add the following entry to .cursor/mcp.json in the project root (for that project only) or to ~/.cursor/mcp.json in your home directory (for all projects):

{
  "mcpServers": {
    "weproxy": {
      "url": "https://weproxy.io/api/mcp"
    }
  }
}

Check that the server shows as green (connected) in the MCP section of Cursor's settings.

VS Code: Create a .vscode/mcp.json file in your workspace:

{
  "servers": {
    "weproxy": {
      "type": "http",
      "url": "https://weproxy.io/api/mcp"
    }
  }
}

The rule is the same for other MCP clients: transport Streamable HTTP, address https://weproxy.io/api/mcp. To test the connection independently of any client, you can use the official MCP Inspector (npx @modelcontextprotocol/inspector).

Example use cases

• Choosing a product: For “I need to manage several social media accounts in Turkey, which proxy should I use?”, the assistant calls recommend_proxy with purpose: social and country: TR and returns the products listed under the social media use case that cover Turkey, with links.
• Comparing prices: For “Compare the 10 GB packages of rotating residential and rotating datacenter”, get_pricing is called for both products; prices come back in the same format as on the site.
• Diagnosing errors: For “I'm getting 407 on my proxy”, diagnose_proxy_error returns that the error is at the proxy layer, the likely cause (wrong credentials, unencoded password, IP not on the whitelist) and the first thing to check, and links to the proxy error codes guide for details.
• Coverage questions: For “Do you have mobile proxies in Poland?”, check_location lists the products that cover the country. Because city-level stock is not stored in the records, the tool makes no claims about city pools; on products that support it, the city is selected in the customer panel.

Security and limits

• Read-only: The server does not create orders, read account data or take payments. Purchases always go through the order page and the customer panel.
• No credentials required: diagnose_proxy_error accepts only the error code. Do not give the assistant your proxy URL, username or password; the server does not ask for them anyway.
• No invented data: Price, stock and country information comes from the product records on the site. When asked about something that is not in the records (for example, city pools), the tool says so explicitly.
• Rate limit: The endpoint is limited to 30 requests per minute per IP. When the limit is exceeded, it returns 429 with Retry-After.
• Usage rules: Proxy use is subject to the acceptable use policy; the MCP server does not change these rules.

If you want to compare products without MCP, the proxy buying guide and the proxy types comparison are good starting points. You can verify that the proxy you connect to works with the proxy checker.

Frequently asked questions

What is the WeProxy MCP server address?

The address is https://weproxy.io/api/mcp and the transport is Streamable HTTP. You add it with this address to Claude, Claude Code, Cursor, VS Code and other clients that support MCP. No API key, account or additional authentication is required; the server is public and read-only.

Is the WeProxy MCP server paid?

No. The server is free, and you do not need a WeProxy account to use it. It returns only catalog, pricing, coverage and guide information. To actually use a proxy, you still need to buy a package or start the Premium Rotating Residential 1 GB trial.

Can the MCP server buy proxies or access my account?

No. All tools are read-only; they do not create orders, take payments or access the customer panel. Your purchases and proxy details are managed only in the WeProxy customer panel. The assistant can give you a product page or an order link, but you complete the transaction yourself.

Are the prices the assistant gives up to date?

Yes. The list_products and get_pricing tools read from the same product records the pricing page uses and return prices in the site's format. No separate price table is kept. If you see a price in the assistant's answer, it is a good habit to check that it came from this tool call.

Do I need to give my proxy password to the assistant?

No, and you should not. The diagnose_proxy_error tool accepts only the error code; it does not ask for a proxy URL, username or password. Since credentials may be stored in your chat history, type only the error code you received instead of sharing them with the assistant.

What should I do if the connection does not work?

First check that the address is entered exactly as https://weproxy.io/api/mcp and that your client supports the Streamable HTTP transport. If you sent many requests in a short time, you may get 429 because of the per-minute limit; wait one minute. If the problem persists, test the connection with MCP Inspector or contact support.