> 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.md).

# Your own strategies through MCP

Turn your trading idea into a strategy in ISA Terminal. Explain the rules to an AI assistant in ordinary language. Through MCP, the assistant prepares the strategy, checks it, and saves it in your terminal. You do not need to write the code yourself.

You can then test it on historical data, request changes, compare versions, and create a bot using the version you choose.

## What appears in the terminal

Your saved strategy appears in **Bots → Strategies**, alongside built-in strategies. It is available in the tester and the bot creation form for the markets it supports.

* **Name and description** explaining its behavior.
* **Settings** you asked to make adjustable, such as position size or indicator periods.
* **Versions** for testing changes while retaining an earlier version.
* **Test results** after a historical run: trades, profit or loss, drawdown, and other metrics.

## Before you begin

1. Run ISA Terminal.
2. [Connect a desktop AI assistant through MCP](/en/isa-terminal/own-strategies/mcp.md).
3. Enable **Strategy authorship** in the MCP settings and click **Save**.

You communicate with the assistant in its own application. Saved strategies appear in the terminal. **Manage bots** is not required to create a strategy or run historical tests; it is required if you ask the assistant to create or start a bot.

## 1. Describe your trading idea

Tell your assistant:

* whether the strategy is for Spot or Futures;
* when to enter and exit;
* whether it can trade long, short, or both;
* the trade size and loss limits;
* which settings you want to adjust in the terminal.

Here is an educational example using your own rules. Replace the conditions with your idea:

> Create my strategy MyCross for Spot, long only. Enter when a fast moving average crosses above a slow moving average. Exit on the opposite crossover. Do not average into the position.
>
> Make the moving-average periods, trade size, and protective stop adjustable in the terminal. First ask me for their values and any missing conditions. Then check the strategy, save it in ISA Terminal, and add a clear description of each setting. Tell me the saved strategy name and version. Do not create bots or start trading.

Answer the assistant's questions before saving: for example which moving averages to use and the units for trade size. These rules determine behavior. Clear conditions make the result easier to verify; “make a profitable bot” does not define usable rules.

## 2. Find your strategy

The terminal checks a strategy before saving it. If the check fails, the assistant must fix the issues and try again.

1. Open **Bots → Strategies**.
2. Find your strategy by name: **MyCross** in this example.
3. Click **Documentation** to read the description the assistant added.
4. Open **Bots → Tester**, select the strategy, and inspect its settings.

Ask the assistant to explain the result:

> Explain when MyCross enters and exits, how its protection works, and what each setting means. Compare this with my original request.

If there is no card, ask whether the assistant actually saved the strategy through MCP or only drafted it. A successful save check does not establish that the strategy will be profitable.

## 3. Test on historical data

In **Bots → Tester**, select a connection, strategy, version, symbol, timeframe, and historical period. Set the fees and start the test.

You can also ask your assistant:

> Test the saved version of MyCross on historical data. First ask me for the connection, symbol, timeframe, date range, and fees. Show profit or loss, drawdown, and trade count. Explain the weaknesses. Do not start live trading.

If the assistant runs the test through MCP, it receives the results and explains them in your chat. To see trades on a chart in the terminal, run the same version with the same settings in **Bots → Tester**.

Check that entries and exits match your idea. Compare several periods, including difficult ones, and review position size as well as the result and drawdown.

## 4. Improve and compare versions

Ask for a specific change:

> Improve MyCross: add an adjustable take-profit while keeping the crossover exit and protective stop. First ask me for the take-profit size. Save a new version, explain the change, and compare it with the previous version on the same symbol, dates, and fees. Do not create bots.

Changed code saved under the same strategy name becomes a new version. You can select versions in the tester and when creating a bot.

Existing bots keep their selected version. A newer-version indicator means another version is available; it does not update the bot automatically. Test the new version first and create a new bot to use it.

## 5. Create a bot using the tested version

1. Open **Bots → Create bot**.
2. Select a connection and your strategy.
3. Choose the tested **Version**.
4. Set the symbol, timeframe, and strategy settings.
5. Create the bot. Start it separately when you are ready.

Use a demo connection for your first run where available. Saving a strategy does not start trading.

With **Manage bots** enabled, you can ask:

> Create a stopped bot using the version of MyCross we tested. First agree with me on the connection, symbol, timeframe, and settings. Show those settings again after creating it. Do not start the bot.

You can then start it manually or explicitly ask your assistant to start it. On a live connection, it will trade with your funds. Monitor its position, orders, and logs in the bot viewer.

## Other requests you can make

* “Make this setting adjustable in the terminal and explain its purpose.”
* “Explain why the strategy opened no trades in this test.”
* “Compare two versions and show where the new one is better or worse.”
* “Write a description so I can understand my strategy's rules and settings a month from now.”

Make one change at a time and check the result. The assistant may misunderstand your idea; a good historical test does not guarantee future profit.

## Delete your own strategy

In **Bots → Strategies**, use the delete button on your strategy card and confirm. If any bots use that strategy, deletion is blocked and the terminal lists those bots. Stopping a bot does not remove this restriction. Deleting bots also removes their history and statistics.

## If a strategy error appears

Open the bot viewer and click the strategy-error indicator for details. Check the timestamp: it may refer to an earlier run.

If strategy decisions have stopped, inspect the position and orders and investigate the error with your assistant. Stop and restart the bot to resume decisions. When stopping it, choose explicitly whether to close or retain its position.

See [Starting and stopping](/en/isa-terminal/kak-sozdat-i-zapustit-torgovogo-bota/zapusk-i-ostanovka.md) for position handling. When contacting support, include the strategy name, version and error text.

Related guides: [Strategy tester](/en/isa-terminal/tester.md), [Creating a bot](/en/isa-terminal/kak-sozdat-i-zapustit-torgovogo-bota/kak-sozdat-bota.md) and [Managing bots](/en/isa-terminal/kak-sozdat-i-zapustit-torgovogo-bota/upravlenie-botami.md).