Skip to main content
2extract is built to be driven by software, not only by people. If you work with AI agents - Claude Code, Cursor, Codex, or something you wrote yourself - there are three ways to plug 2extract into them.

MCP Server

Let an agent create proxies, resolve geo targeting, set spend limits, and read usage.

LLM References

Our whole documentation portal as two machine-readable text files, following the llms.txt standard.

Docs MCP Server

Let an MCP client search this documentation live, instead of loading it into context.

​
Which one do you need?

The three are complementary, and most teams end up using more than one. The distinction that matters: the MCP Server acts - it changes things in your account and costs money. The other two only read - they are documentation in a shape a model can consume.

​
What the MCP Server does

Instead of clicking through the dashboard, you describe the job:
Collect gaming-laptop prices from Amazon in Germany, the UK and Japan.
The agent resolves the countries, picks a plan, checks your balance, creates a proxy named after the task, sets a traffic cap, and hands back connection strings for each country - ready to paste into your tools.

Quick Start

Connect your first client in about two minutes.

Usage Examples

Full sessions, from the request to the connection string.

​
Supported clients

Any client that speaks the Model Context Protocol over Streamable HTTP works. We keep setup guides for the most common ones:

Claude Code

Claude Desktop

Codex

Cursor

VS Code

Windsurf

Cline

Other clients

​
What it costs

The MCP server itself is free. You pay for the proxies your agent creates, at the same pay-as-you-go rates as everything else - see Billing & Usage.
An agent with a proxies:write key can create billable resources on your account. Scope the API key to what the agent actually needs, and set a spend limit on every proxy. See Provisioning & Cost Control.