Skip to main content
The 2extract MCP server exposes your account to an AI agent as a set of callable tools. The agent can create and configure proxies, resolve geo targeting down to city and ASN, cap traffic and spend, and read balance and usage - without you touching the dashboard or writing any code. It speaks the Model Context Protocol, so any MCP-capable client can connect to it.

​
Endpoint

Keep the /mcp path in your client configuration. The bare host serves a landing page, not the protocol.

​
Authentication

Use your regular 2extract API key. There is no separate MCP key type and nothing extra to enable.
Create a key in the Dashboard under API Keys. Full details, including how keys are stored and rotated, are on the API Keys page.

​
Scopes an agent needs

Each key carries scopes that gate which tools will work. Grant only what the agent actually needs.
proxies:write does not include proxies:read - the scopes are independent. An agent almost always reads before it writes, so a write-only key fails partway through most workflows. Grant both.

​
What the server exposes

MCP servers can offer three kinds of things. This one offers all three.
Everything the agent can do: account balance and usage, geo lookup, plan lookup, and full proxy lifecycle. Two of them are destructive and ask for your confirmation first.See the Tools reference.
Ready-made multi-step routines: create a proxy for a stated purpose, build a connection string, report on monthly cost, clean up idle proxies. Clients that support prompts expose them as slash commands.See the Prompts reference.
Reference documents the agent reads by itself, so it understands what came back from a tool instead of guessing. Nothing to call and nothing to configure.

​
A worked example

You ask:
Collect gaming-laptop prices from Amazon in Germany, the UK and Japan.
The agent, on its own:
1

Resolves the countries

Calls listGeoCountries to turn “Germany, the UK and Japan” into values it can target with.
2

Picks a plan and checks funds

Calls listProxyPlans and getAccountBalance before spending anything.
3

Creates the proxy

Calls createProxyResource with a name and description that reflect the task, so the resource is recognisable later in your dashboard.
4

Caps the spend

Calls setProxyLimits to put a monthly ceiling on it.
5

Hands back connection strings

One per country, ready to paste into your tools.
The full session, with real output, is on the Usage Examples page.

​
Next steps

Quick Start

Connect a client and run your first request.

Tools

Everything the agent can reach, and what it cannot do.

Prompts

The four built-in workflows.

FAQ

Keys, scopes, limits, errors, and cost.