> ## Documentation Index
> Fetch the complete documentation index at: https://docs.2extract.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Prompts

> Four guided workflows the 2extract MCP server ships with, exposed as slash commands in clients that support MCP prompts.

Tools are single actions. **Prompts** are routines built on top of them - a sequence the server already knows how to run, so you do not have to spell it out.

Clients that support MCP prompts surface them as slash commands. Type `/` in your agent and they appear alongside the client's own commands.

***

## The four workflows

| Prompt                    | Arguments                                                             | What it does                                                           |
| :------------------------ | :-------------------------------------------------------------------- | :--------------------------------------------------------------------- |
| `create-proxy-resource`   | `purpose` <Icon icon="asterisk" size={12} />, `proxy_type`, `country` | Creates a proxy for a stated job and returns a ready connection string |
| `build-connection-string` | `proxy_id`, `purpose`                                                 | Assembles a connection string for a proxy that already exists          |
| `monthly-cost-report`     | `period` <Icon icon="asterisk" size={12} />                           | Traffic and spend for a period, with warnings                          |
| `cleanup-unused-proxies`  | none                                                                  | Finds idle proxies and deactivates them after you confirm              |

***

## create-proxy-resource

Describe the job. The prompt recommends a proxy type and geo setup, creates the resource with a name and description that match the task, and finishes with a connection string you can paste straight into your tools.

<ParamField path="purpose" type="string" required>
  What the proxy is for, in plain language - `collecting Amazon product prices in the US`.
</ParamField>

<ParamField path="proxy_type" type="string">
  `residential` or `mobile`. Omit it and the agent recommends one based on the purpose.
</ParamField>

<ParamField path="country" type="string">
  Default country, as a name or ISO code - `US`, `Germany`. Omit it and the agent infers one from the purpose.
</ParamField>

The name it generates follows our naming rules automatically: lowercase, digits and underscores only, no hyphens. Names are immutable, so this matters - see [Tools](/ai/mcp-server/tools).

***

## build-connection-string

The same recommend-then-assemble step as above, but for a proxy that already exists. Useful when the proxy was created in the dashboard and you now want the right username parameters for a specific job.

<ParamField path="proxy_id" type="string">
  Which proxy to build the string for. Omit it and the agent asks, or picks from your list.
</ParamField>

<ParamField path="purpose" type="string">
  What the connection is for. Drives the protocol, geo, and session recommendations.
</ParamField>

The output is a full `username:password@host:port` string with the geo and session parameters encoded in the username. The format itself is documented under [Authentication](/proxy-products/configuration/authentication).

***

## monthly-cost-report

Traffic and spend over a period, per proxy, with the outliers called out: proxies burning traffic unusually fast, proxies sitting idle, and a low balance.

<ParamField path="period" type="string" required>
  Accepts natural language - `this month`, `last 30 days`, `March`.
</ParamField>

Read-only. Nothing is created, changed or charged.

***

## cleanup-unused-proxies

Finds proxies with zero traffic over the last 30 days and deactivates them, after showing you the list and waiting for confirmation.

No arguments.

<Check>
  This prompt **never deletes**. It only deactivates, which is reversible - set a proxy back to `active` and it resumes.
</Check>

***

## Next steps

<CardGroup cols={2}>
  <Card title="Usage Examples" icon="terminal" href="/ai/mcp-server/usage-examples">
    Full sessions, including one driven by a prompt.
  </Card>

  <Card title="Tools" icon="wrench" href="/ai/mcp-server/tools">
    The individual actions these workflows are built from.
  </Card>
</CardGroup>