> For the complete documentation index, see [llms.txt](https://docs.ispecalgo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ispecalgo.com/en/isa-terminal/own-strategies/mcp.md).

# Connect your AI assistant

MCP connects a desktop AI assistant to ISA Terminal. You can ask it to create your own strategy, save it in the terminal, test it on historical data, and improve it based on the results.

You talk to the assistant in its own application. The saved strategy appears in ISA Terminal. You do not need to write the code yourself.

[**Your own strategies via MCP**](/en/isa-terminal/own-strategies.md) explains the full process with example requests.

## What you need

* ISA Terminal running on your Windows computer or Windows VPS.
* A desktop AI assistant with MCP support installed on the same computer.

Web-only assistants cannot use this local connection. Keep the terminal running while working with your assistant.

## Connect the assistant

1. In ISA Terminal, click the **gear icon** in the top-right corner.
2. Open **MCP** and enable **MCP server**.
3. Select the permissions you need. To create your own strategies, enable **Strategy authorship**.
4. Click **Save**. You do not need to restart the terminal.
5. Copy the complete text from **Prompt for the agent** and send it to your assistant. Follow any setup steps it requests.
6. Fully restart your assistant so it loads the connection settings. Leave ISA Terminal running.

To check the connection, ask:

> Show my bots and their status. Do not change anything.

## Choose the assistant's permissions

| Permission              | What it allows                                                                  |
| ----------------------- | ------------------------------------------------------------------------------- |
| **Strategy authorship** | Check and save your own strategies, read their code, and delete them            |
| **Manage bots**         | Create, configure, start, stop, and delete bots                                 |
| **Manage connections**  | Create, delete, enable and disable connections; change supported position modes |
| **Manage presets**      | Create, change, delete, import and export presets                               |
| **Manage indicators**   | Add, configure and remove indicators on charts                                  |
| **Change settings**     | Change language, interface scale, autostart and other available settings        |
| **Send bug reports**    | Send reports with information for investigating a problem                       |
| **Allow all**           | Enable all permissions above                                                    |

Viewing data and running historical tests do not require **Manage bots**. Creating a strategy requires **Strategy authorship**. Creating or starting a bot requires **Manage bots**.

The MCP server is disabled by default. **Strategy authorship** and bug reporting are selected in the default permissions. Check the list before enabling MCP and keep only the permissions you want to grant.

## Your first strategy request

> I want to create my own strategy in ISA Terminal. Help me define entry rules, exits, and risk limits. After we agree on them, check and save the strategy, then help me test it on historical data. Do not start live trading.

Saving the strategy and starting a bot are separate actions. Existing bots keep their selected strategy version when you save an update.

## What you can ask the assistant to do

### Create your strategy

With **Strategy authorship**, the assistant can prepare, check and save a strategy from your description, then revise it and save new versions.

> Help create my strategy. First clarify entries, exits and risk limits. Then check and save it with a clear description. Do not create bots or start trading.

See [Your own strategies](/en/isa-terminal/own-strategies.md).

### Inspect bots and positions

The assistant can read bot status, open positions, active orders, trade history and profit/loss.

> Show which bots are running, where positions are open and which errors appeared today.

### Manage bots

With **Manage bots**, it can create, configure, start or stop one or several bots. Specify what happens to positions:

> Stop this bot and leave its position open.

> Stop this bot and close its position.

Closing on stop uses a market order. On a live connection this trades with your funds. The same [bot allocation rules](/en/isa-terminal/birzhi-i-podklyucheniya/one-way-rezhim.md) apply as in the interface.

Deleting removes local history and statistics. If you ask to delete a bot while retaining its position, that position stays on the exchange without this bot's management or stop. See [Managing bots](/en/isa-terminal/kak-sozdat-i-zapustit-torgovogo-bota/upravlenie-botami.md).

### Check connections and position mode

The assistant can show connections, available coins and position mode. Changes require **Manage connections**.

> Show the position mode of my futures connection.

> Switch this connection to Hedge Mode.

See [Position modes](/en/isa-terminal/birzhi-i-podklyucheniya/one-way-rezhim.md) for conditions and verification. Disabling a connection stops its associated bots. Check which bots use a connection before deleting it.

### Inspect charts and configure indicators

The assistant can read candles and indicator values. Enable **Manage indicators** to work with user indicators. Bot and tester charts show strategy indicators; arbitrary catalogue indicators cannot be added there.

> Show what happened on the BTC-USDT chart during the selected period.

See [Indicators](/en/isa-terminal/indikatory.md).

### Compare historical settings

> Test several configurations of the selected strategy on one coin over the same period. Compare profit, drawdown and trade count. Do not start live trading.

Testing does not require bot-management permission. Saving a preset or changing a bot requires the respective permission. See [Strategy tester](/en/isa-terminal/tester.md).

### Work with presets

With **Manage presets**, the assistant can save settings, prepare variants and import/export presets.

> Save this bot's settings as a preset named “GRID BTC”.

See [Presets](/en/isa-terminal/presety-strategii.md).

### Investigate an error

> Read this bot's errors for today and explain them in simple terms.

> Prepare and send a support report describing the problem and including diagnostic data.

Sending requires **Send bug reports**. See [Bug reports](/en/isa-terminal/baza-znanii/kak-otpravit-bag-report.md) for the included data and preparation.

## If the connection fails

1. Check that ISA Terminal is running.
2. Check that **MCP server** is enabled and the settings have been saved.
3. Copy the current connection prompt from the terminal again.
4. Restart your assistant.
5. If an action is refused, check the permission for that action.

The assistant can make mistakes. Its service may receive the data it reads, including the code of your own strategies when you allow it. Enter exchange keys and the Hyperliquid API-wallet private key directly in the terminal's connection form.

## Limits

The assistant may reach a wrong conclusion or choose unsuitable settings. Review results before live trading. The connection does not work when the terminal is closed; changes require the relevant permissions. Chart data is a snapshot at the time of the request. Backtest results do not guarantee profit.

Do not share API keys with the assistant unnecessarily. Try management tasks on a demo connection first.