Proxies your AI agent sets up itself

Connect the 2extract MCP server to Claude Code, Cursor, Codex or any MCP client. Describe the job; the agent creates the proxy, caps it and hands back the connection strings.

One server acts, the other reads

There are two ways to plug 2extract into an agent, and most teams use both.

The MCP server acts

It works in your account with your API key: it creates and configures proxies, looks up countries and cities, sets limits and reads usage. Connect it at https://mcp.2extract.com/mcp.

Creating a proxy costs money, so give it only the scopes it needs.

The docs read

The documentation is available to models as llms.txt and llms-full.txt, and as a docs MCP server at https://docs.2extract.com/mcp that searches it on demand.

They change nothing and cost nothing.

From one prompt to a working proxy

Ask for a proxy in Berlin, capped at 2 GB. The agent finds the city, picks the plan, creates the proxy, sets the cap and wires it into your scraper.

~/projects/price-tracker

Example session. Account ID, password and IP are illustrative.

  1. 1Get an API key. Sign up, top up from $10 and create a key under API keys in the dashboard.
  2. 2Connect. One command adds the 2extract MCP server to Claude Code, Cursor or any MCP client.
  3. 3Describe the job. Country, city, session and budget, in plain language.
  4. 4The agent builds it. It finds the city, creates the proxy and sets the cap.
  5. 5It ships the code. The connection string lands in your scraper, and the first request runs.

What the agent can do

Each tool needs a scope on the API key, so you decide how far an agent may go.

What the agent can do

  • Create and manage proxies

    Create, update, deactivate or delete a proxy and rotate its password, with proxies:write.

  • Resolve targeting

    Turn "Berlin" or "T-Mobile US" into the country, city or carrier values a username needs, with geo:read.

  • Cap the spend

    Set daily or monthly limits in GB or USD as it creates a proxy, so a run cannot drain the balance.

  • Read balance and usage

    Check the balance, the traffic and spend per proxy and the payment history, read-only.

  • Scoped keys

    The same API keys as the public API. Give an agent that only needs to look a read-only key.

  • Know the product

    llms.txt and the docs MCP server let any model answer from our documentation.

Connect it in about two minutes: one command in Claude Code, one block of JSON elsewhere.

AI agent questions

Every tool and client setup is in the MCP documentation.

Still have a question?

Talk directly to the engineers who built the product. No chatbots, no first-level support scripts.

Your agent's first proxy is one prompt away

Sign up with Google, GitHub or email, top up from $10 and pay per GB. No commitment.

claude mcp add --transport http 2extract https://mcp.2extract.com/mcp --header "Authorization: Bearer •••"