2extract

2extract MCP Server

VS Code asks for the API key on install and does not store it in the config. Cursor installs with a placeholder: replace 2xt_your_api_key in mcp.json with your key.

Remote Model Context Protocol server for 2extract. It lets an AI agent create and manage residential and mobile proxies, pick geo targeting down to city, ZIP or carrier, set traffic and spend limits, and report on usage and cost.

This is a hosted server. There is nothing to install or run locally: your MCP client connects to the URL below with your 2extract API key.

Get an API key

1. Sign up or log in to 2extract.
2. Open API keys and create a key.
3. Grant the scopes the agent needs: proxies:read, proxies:write, balance:read, stats:read, geo:read. Write scopes do not include read access, so most workflows need both proxies:read and proxies:write.

A read-only key (no proxies:write) is enough for reporting and lookups.

Connect

Claude Code

claude mcp add --transport http 2extract https://mcp.2extract.com/mcp \

--header "Authorization: Bearer 2xt_your_api_key"

Codex CLI

The key is read from the EXTRACT_API_KEY environment variable; Codex adds Bearer itself:

export EXTRACT_API_KEY=2xt_your_api_key

codex mcp add 2extract --url https://mcp.2extract.com/mcp --bearer-token-env-var EXTRACT_API_KEY

Or edit ~/.codex/config.toml (or .codex/config.toml in a trusted project):

[mcp_servers.2extract]

url = "https://mcp.2extract.com/mcp" bearer_token_env_var = "EXTRACT_API_KEY"

Gemini CLI

gemini mcp add -s user --transport http \

--header "Authorization: Bearer 2xt_your_api_key" \ 2extract https://mcp.2extract.com/mcp

Or edit ~/.gemini/settings.json (or .gemini/settings.json in a project):

{

"mcpServers": { "2extract": { "httpUrl": "https://mcp.2extract.com/mcp", "headers": { "Authorization": "Bearer 2xt_your_api_key" } } } }

OpenCode

opencode.json in your project (or ~/.config/opencode/opencode.json). The key is read from the EXTRACT_API_KEY environment variable:

{

"$schema": "https://opencode.ai/config.json", "mcp": { "2extract": { "type": "remote", "url": "https://mcp.2extract.com/mcp", "enabled": true, "headers": { "Authorization": "Bearer {env:EXTRACT_API_KEY}" } } } }

Claude Desktop

claude_desktop_config.json:

{

"mcpServers": { "2extract": { "type": "http", "url": "https://mcp.2extract.com/mcp", "headers": { "Authorization": "Bearer 2xt_your_api_key" } } } }

Cursor

~/.cursor/mcp.json or .cursor/mcp.json:

{

"mcpServers": { "2extract": { "url": "https://mcp.2extract.com/mcp", "headers": { "Authorization": "Bearer 2xt_your_api_key" } } } }

VS Code

.vscode/mcp.json (the key is requested on first use and not stored in the file):

{

"inputs": [ { "type": "promptString", "id": "2extract-api-key", "description": "2extract API key", "password": true } ], "servers": { "2extract": { "type": "http", "url": "https://mcp.2extract.com/mcp", "headers": { "Authorization": "Bearer ${input:2extract-api-key}" } } } }

Cline

Open the Cline panel, click MCP Servers, then Configure MCP Servers, and add to cline_mcp_settings.json:

{

"mcpServers": { "2extract": { "type": "streamableHttp", "url": "https://mcp.2extract.com/mcp", "headers": { "Authorization": "Bearer 2xt_your_api_key" }, "disabled": false } } }

Keep "type": "streamableHttp": without it Cline falls back to the older SSE transport.

Other clients

Any client that supports remote MCP servers works. Give it the endpoint URL, the Streamable HTTP transport and the Authorization header.

Tools

Account

Geo targeting

Plans

Proxies

Confirmation for destructive tools happens in your client. If the client does not ask, any key with proxies:write can run them, so scope keys accordingly.

Prompts

Example requests

• "Create a residential proxy in Germany, Berlin, for price monitoring, capped at 5 GB a month."
• "Give me a sticky-session connection string for my serp_us proxy."
• "How much did I spend on traffic last month, per proxy?"
• "Which proxies had no traffic in the last 30 days? Deactivate them."
• "Find mobile carriers in the US I can target."

Documentation

• MCP server overview
• Quick start
• Tools reference
• Prompts
• Usage examples
• FAQ
• Connection page

Support

• Email: support@2extract.com
• Issues with this listing: open an issue in this repository

Legal

• Terms of Service
• Privacy Policy

The server source code is not published. This repository holds the public listing, client configuration examples and the registry manifest (server.json).