Webshare Launches an MCP Server: Manage Your Proxies From Claude or Cursor, Free on All Plans

Webshare, the budget proxy provider we reviewed here, has shipped an MCP server: a connector that lets an AI assistant such as Claude, Claude Code or Cursor read and, if you allow it, manage your proxy account in plain English. It is free on every Webshare plan, including the no-card free tier, and the server address is simply https://mcp.webshare.io/.

Instead of opening the dashboard to find out why half your requests failed overnight, you ask your assistant. Below is what the server actually does, how the permission model works, and where we would be careful.

What MCP is, in one paragraph

MCP (Model Context Protocol) is an open standard for plugging external tools into AI assistants. An MCP server exposes a set of actions ("list proxies", "get usage stats") and the assistant decides when to call them based on what you ask. Claude, Claude Code, Cursor and most other agent clients speak it natively, so one server works across all of them. Webshare's is a remote server: nothing to install, you point the client at a URL and log in.

What you can ask it

Webshare's launch examples are a fair summary of the scope:

The first two are read-only. The next two change your account. The last one is a quote, and quoting is as far as money goes, see below.

The permission model

This is the part worth reading before you connect anything.

• Read-only by default. On first login you choose what the assistant can access. Without opting in, it can look but not touch.
• Write access is opt-in, scoped at login. Replacing proxies and editing the allowlist need it; listing and stats do not.
• No spending, ever. The assistant can quote prices but cannot buy, upgrade, or touch payment methods. That boundary is enforced server-side, not left to the model's good behaviour.
• Revoke in one click from the Webshare dashboard.

That is a sensible design. Most of the risk in letting an agent run your infrastructure is an unexpected purchase or a destructive change; Webshare has walled off the first entirely and gated the second.

Setup

1. Add https://mcp.webshare.io/ as a remote MCP server in Claude (Settings → Connectors), Claude Code (claude mcp add --transport http webshare https://mcp.webshare.io/), Cursor, or any other MCP client.
2. Log in to Webshare when prompted and pick the access level.
3. Ask something: "List my proxies grouped by country."

Webshare says the whole thing takes under a minute. In our experience with remote MCP servers that is accurate; the only variable is how long the OAuth login takes.

▶ Try the Webshare MCP on the free plan

Who this is actually for

• Developers running scrapers who already live in Claude Code or Cursor. Checking proxy health without context-switching to a browser tab is the obvious win, and "replace everything failing over X %" is a chore that was begging to be automated.
• Small teams without a proxy ops person. The error-summary question replaces a dashboard you otherwise never open until something breaks.
• Anyone evaluating Webshare. The MCP works on the free tier (10 datacenter proxies, 1 GB a month, no card), so you can test the integration before paying.

Less useful if you run proxies through your own code against Webshare's REST API. The MCP does not add capabilities the API lacks; it adds a conversational layer on top of them. Automated pipelines should keep calling the API directly.

Where we would be careful

• Keep read-only unless you need writes. "Replace proxies failing over 5 %" is convenient, but a mis-phrased request, or a model that misreads your intent, can rotate IPs you wanted to keep. Enable writes for the session you need them, then revoke.
• Prompt injection is real for agents. If your assistant also reads web pages or scraped content, text in those pages can try to steer it. An agent with write access to your proxy account is a bigger target than one without. This is a general MCP caveat, not a Webshare flaw, but it is why the read-only default matters.
• A proxy manager is not a VPN. Our review spells this out: Webshare is a tool for developers and data teams who need many IPs, not for hiding your own browsing. The MCP does not change that.

Our take

To our knowledge this is the first budget proxy provider to ship an official MCP server, and the permission design is better than many first attempts we have seen from SaaS vendors: no payment surface, writes off by default, one-click revoke. For Webshare's core audience of developers it is a genuinely useful addition at no extra cost. If you are already a customer, connect it in read-only mode and ask the errors question. If you are not, the free tier is the lowest-risk way to see whether a conversational proxy manager fits your workflow.

For context on Webshare's recent product moves, see our coverage of the USA Dedicated ISP restock and Colombia launch and the Brazil residential location.

FAQ

Does the Webshare MCP cost extra?

No. It is included on every plan, including the free tier.

Which AI clients does it work with?

Claude (desktop and web), Claude Code, Cursor, and any other client that supports remote MCP servers.

Can the AI buy proxies or change my billing?

No. It can quote prices but cannot purchase, upgrade, or access payment methods.

Is it read-only?

By default, yes. Write access for actions such as replacing proxies or editing the IP allowlist is a separate opt-in at login, and can be revoked at any time.

What is the server URL?

https://mcp.webshare.io/

Details as announced by Webshare on 19 October 2026. We have not yet load-tested the server ourselves; we will update this page after a hands-on run.