Log in

MCP Server for Mobile Proxies: Connect Claude, Cursor and VS Code

A mobile proxy MCP server is a connection point through which an AI agent manages a proxy account the same way a user does in the dashboard: it checks the balance and prices, picks a country and operator, buys and renews channels and rotates IPs. In 2026 agents in Claude, Cursor and VS Code increasingly carry out whole work tasks on their own — from data collection to ad verification — and the network layer becomes one more tool they need at hand.

What MCP is and why mobile proxies need it

Model Context Protocol (MCP) is an open protocol that AI assistants use to call external tools. A service describes a set of actions, and the agent decides which one fits the current request, passes the parameters and gets the result.

For mobile proxies this removes manual work between tasks. Rotating an IP or renewing a channel used to mean opening the dashboard or writing a script against the API. With an MCP server the agent does it from a chat message: “renew the proxies that expire this week” or “rotate the IP of the scraping proxy and show the new address”.

What an agent can do through the LTESpace MCP server

  • check the account balance and currency;
  • list proxies with connection details, filtered by country and order;
  • show available countries, cities and operators — more on mobile proxy geography;
  • show prices by plan and period and how many channels can be bought right now;
  • create purchase and renewal orders and pay for them from the balance;
  • rotate the IP of proxies with manual rotation and return the old and new address.

The agent accepts a country as an ISO code (RU, GE) or as a name from the directory, so a request like “proxies in Georgia” needs no technical formatting.

How to connect the mobile proxy MCP server

  1. Sign up at LTESpace and issue an API key in the dashboard settings. Right after issuing it, the dashboard shows a ready-to-run connection command with the key already filled in.
  2. Add the server to your client. For Claude Code a single command is enough:
claude mcp add --transport http ltespace https://api.ltespace.com/mcp \
  --header "Authorization: Bearer <api_key>"
  1. For Cursor and VS Code, the https://api.ltespace.com/mcp endpoint and the Authorization header go into an mcp.json file. Ready-made configs are in the API documentation, in the “MCP for AI agents” section.

There is nothing to install: the server runs remotely, and the client only needs the address and the key.

Purchases stay under the user’s control

Buying and renewing always take two steps. First the agent creates an order and gets the amount — nothing is charged. Then, after confirmation, it calls a separate payment tool. That tool is marked as irreversible, and clients ask for consent before running it. Paying the same order again does not charge twice.

It is best not to enable auto-approval for the payment tool: that way the balance is never spent without the user’s explicit consent.

Where it is used

  • scraping and monitoring: the agent rotates the IP between batches of requests and makes sure channels do not expire mid-collection — see mobile proxies with rotation for rotation intervals;
  • automation: the agent buys extra channels for a new task and renews the ones in use;
  • location checks: the agent picks a city and operator, buys a channel for one day and returns the connection details;
  • spend control: the agent combines the balance, active proxies and expiry dates into one answer.

When to choose MCP and when the API

  • MCP — when a person sets the task in a chat with the agent and proxy actions are occasional;
  • MCP — when the agent already runs the whole process and proxies are just one of its tools;
  • API — when a fully automatic pipeline without human involvement is needed;
  • API — when IP rotation and purchase logic is hard-coded and must not depend on model decisions.

MCP and the API share the key, data and limits, so they can be combined: a script works through the API while the agent handles one-off actions.

Summary

A mobile proxy MCP server turns channel management into a set of AI agent tools: balance, prices, purchases, renewals and IP rotation are available on request in chat. Connecting takes a single command, and payment stays under the user’s control.

FAQ

Do I need to install anything to use the LTESpace MCP server?

No. The server runs remotely at https://api.ltespace.com/mcp. The client only needs this address and an API key from the dashboard — no packages, Node.js or Docker are required.

Can the agent spend money without confirmation?

A purchase takes two steps: first an order is created and its amount is shown, with nothing charged. Only a separate payment tool charges the balance, and it is marked as irreversible, so Claude, Cursor and VS Code ask for confirmation before calling it. As long as auto-approval is not enabled for it, no payment goes through without the user's explicit consent.

How is MCP different from the regular API?

The API is built for code: a developer writes the requests and handles the responses. The MCP server exposes the same capabilities to an AI agent, which picks the right tool itself from a request in chat. The key, data and limits are shared: an order created by an agent is visible in the dashboard and through the API.

Which clients are supported?

Claude Code, Cursor, VS Code and any other client that connects to a remote MCP server over HTTP with an authorization header. claude.ai and ChatGPT connectors, which require OAuth sign-in, are not supported yet.

Can the agent rotate the IP of any proxy?

Only of proxies that support manual IP rotation by link. Other proxies change their address on the plan's timer, and the agent reports that manual rotation is not available for them.