Axi MT5 Claude MCP Setup: Connect Your MT5 Account to Claude in Plain Language

Introduction

Axi’s MCP integration lets you talk to your MetaTrader 5 account through Claude instead of clicking through the MT5 terminal for every check. You can ask for a live price, review open positions, or adjust a stop loss in plain language, and Claude carries out the request through the Model Context Protocol. This tutorial walks through the setup exactly as Axi documents it, shows how to verify the connection with a read-only question first, and explains the permission and safety checks that matter before you approve any trade. It is written for an Axi client who already has an active MT5 account and a Claude account, and it assumes no coding and no server of your own.

Quick answer

Add Axi as a custom connector in Claude with the server URL https://mcp.axi.com/mcp, sign in with your Axi credentials, approve the permissions, and confirm the connection with a read-only balance question before any trade.

Evidence

Axi announced the integration on October 14, 2026, in a GlobeNewswire release from Sydney, describing it as a connection between eligible MT5 accounts and Claude, Anthropic’s AI assistant. The release states that eligible clients can access live market data, track positions, execute trades, and update risk parameters through Claude. Axi describes itself in the same release as a global online FX and CFD trading company serving thousands of clients across more than 100 countries, as of October 2026. A practical plan number matters too: the Free plan allows one active custom connector at a time, so Axi must be your single custom connector on Free, while paid plans allow more.

Axi frames the limits of the tool plainly, and that framing should shape how you use it. In its help documentation, Axi writes that Claude “is not an automated strategy or Expert Advisor (EA),” and that it acts only when a client asks, unless the client has set a specific action to “Always allow” in Claude’s permission settings. The same help documentation adds that Claude “is not a financial advisor and that its answers are not trade recommendations.” Those two sentences are the safety model for the whole setup: you stay the decision maker, and every trade still needs your approval.

The primary sources for the steps below are Axi’s help article on connecting an Axi account to Claude, which documents the Client Portal route, the manual URL route, and the permission screen, and Axi’s help article explaining what the Axi MCP connection is, which documents the active MT5 requirement, the plan rules, and what the connection is not. The protocol itself is documented in the Model Context Protocol introduction, which describes MCP as an open protocol for connecting AI applications to external tools and data sources. If you are new to MCP in general, start with our MCP server tutorial: what it is and how it works, and if you have connected other servers to Claude before, compare the flow with our guide to connecting an MCP server to Claude Desktop.

Prerequisites

You need an active Axi MT5 account, because the connection cannot be completed with a closed or archived account, an MT4-only account, or an Axi trading platform-only account. You need your own Claude account at claude.ai, on any plan, because the connector works on the Free plan as well as Pro, Max, Team, and Enterprise. You need access to either the Axi Client Portal or the Axi mobile app if you want the portal route, or just a browser tab with Claude open if you want the direct route. You do not need to install anything, run a server, or write a configuration file, because Axi hosts the MCP server and Claude connects to it remotely.

Before you start, decide which account Claude will touch. If you have both a demo and a live MT5 account, test the full flow on the demo account first. The permission screen covers placing and managing trades on MT5 demo and live accounts, so the safest first run is one where a mistake costs nothing. Also decide your approval policy in advance: leave trade tools on per-action approval, and do not switch any trading tool to Always allow until you have watched several approved trades behave exactly as you expected.

Step-by-step guide

Step 1: Confirm your MT5 account is eligible

Sign in to the Axi Client Portal or the Axi mobile app and confirm that you have an active MT5 account listed. An account that is closed or archived will not connect, and neither will an account that exists only on MT4 or on the Axi trading platform. If you see only an MT4 account, stop here and open an MT5 account first, because every later step will fail at the authorisation stage without one. If you hold several MT5 accounts, note which one you intend to connect, because you will authorise access through your Axi login and you should be able to recognise that account’s balance and positions in the verification step.

Step 2: Start from the Axi Client Portal or app

In the Axi Client Portal, go to Settings, then MCP Management. In the mobile app, open the same MCP settings area. Axi offers two ways forward from here. The first is the automatic redirect: click Connect, and you are redirected to the Claude Connectors page to finish setup. The second is the manual copy: click Copy next to the unique MCP server URL, which Axi publishes as https://mcp.axi.com/mcp, and keep that URL ready to paste into Claude. Either route leads to the same Claude screen, so choose the redirect if you want fewer steps and the manual copy if you prefer to see the exact URL you are adding. If the MCP settings page tells you that you cannot connect, recheck Step 1, because that message means no eligible active MT5 account was found.

Step 3: Add Axi as a custom connector in Claude

Open Claude and go to Customize, then Connectors, or visit the connectors page directly from the redirect in Step 2. Click the add button, labelled + Add or Add custom connector, and paste the MCP server URL https://mcp.axi.com/mcp. Give the connector a name you will recognise, such as Axi, and click Continue or Add. If you are not already signed in to your Axi account, Claude redirects you to sign in with your Axi credentials at this point. Axi’s support team can guide you through these steps by live chat or email, but it cannot set up the connection on your behalf or create a Claude account for you, so the sign-in must be yours.

Step 4: Review the permissions and accept the disclaimer

Read the permission screen before you click anything. According to Axi’s help documentation, the permissions may include access to your account information, trading functionality, and offline access. The detailed list on the screen covers reading Axi account data, positions, orders, and live quotes, and placing and managing trades on MT5 demo and live accounts. The screen also shows a disclaimer acknowledgement checkbox, and the connection cannot be completed without your acknowledgement. Only grant permissions you actually want Claude to have. If you only want market data and position checks, think carefully before accepting trade placement, because that permission is what lets a chat instruction become a real order. When you are satisfied, click Accept to continue.

Step 5: Verify with a read-only question first

Do not start with a trade. Start a new chat with the Axi connector enabled and ask a question that cannot move money, such as asking for your account balance and your open positions. Compare every number Claude returns against the same figures in the MT5 terminal or the Axi Client Portal. If the balance matches and the open positions match, the connector is reading the right account. If any figure differs, stop and recheck which account you authorised, because a mismatch here is a warning that should be resolved before any order is discussed. Once the read-only check matches, try a second read-only question, such as the live price of an instrument you already follow, and confirm that the quote looks current rather than stale.

Step 6: Approve one small trade deliberately, on demo first

Only after the read-only checks pass, and only on a demo account for your first trade, ask Claude to place a small order and watch the approval step. Trade actions require your explicit approval in the chat before they go through, so Claude should present the order details and wait for you to confirm. Read the instrument, direction, volume, and any stop loss or take profit in that approval prompt as if you had typed the order yourself, because once you approve, it is a real order on that account. After approval, check the trade history in MT5 or the Client Portal and look for the comment tag described in the troubleshooting section. If the tag is present and the order matches what you approved, the loop is working end to end. Repeat the same careful approval on your live account only when you are comfortable with the demo behaviour.

Step 7: Manage the connection over time

Once connected, Claude reconnects automatically on future visits, so you do not need to repeat the setup every time. Manage the connector from Claude’s connector settings, where you can disconnect it, reconnect it after a dropped session, and control which tools it may use. If you ever want Claude to stop trading, disconnecting the connector is the clean break, and it is faster than trying to police individual prompts. Review the connection after any change to your accounts, such as closing an MT5 account or changing your Axi login. For wider permission habits that apply to every MCP server you connect, read our guide to securing multi-agent MCP networks.

Troubleshooting

The MCP settings page says I cannot connect

This almost always means there is no eligible active MT5 account behind your login. Closed, archived, MT4-only, and Axi platform-only accounts can open the MCP settings page but cannot connect, and the page will say so. The fix is to open or reactivate an MT5 account under the same Axi login, then return to Settings, then MCP Management and try again. If you do have an active MT5 account and still see the message, sign out of the portal completely and sign back in, because a stale session can show the wrong account state.

Claude says the Free plan connector limit is reached

Claude’s Free plan permits a maximum of one active custom connector at a time. If another custom connector is already active, adding Axi fails with a limit error. The fix is to remove the other active custom connector in Claude’s connector settings, or to upgrade your Claude plan through Anthropic if you need several connectors at once. This is a Claude plan rule, not an Axi restriction, so Axi Support cannot lift it for you.

There is no Add connector option in Claude

You may be signed in to an enterprise or company Claude account whose administrator restricts custom connectors. On company or Team accounts, the workspace administrator controls this setting in the company’s Claude admin settings, not Axi. Ask your organisation’s Claude administrator to enable custom connectors. On a personal account, the option should be present, so if it is missing there, check that you are signed in to the personal account and not a work workspace, and contact Anthropic support through the Claude Help Center if the problem persists.

The connection fails or the pasted URL is wrong

Claude does not currently support editing a custom connector URL in place. If you pasted the wrong server URL, or the connection fails to initialise, delete the custom connector entirely inside Claude, copy a fresh URL string from your Axi portal settings, and create a new custom connector with https://mcp.axi.com/mcp. Do not try to patch the existing entry, because the stale URL stays in place. If the error says a connector with this URL already exists in your organisation, cancel the new addition and go to Customize, then Connectors, then Axi, and click Connect or re-authenticate from there.

A trade looks wrong, or I do not recognise a trade

Check the Comment column of your trade history first. Every trade executed through Claude is automatically tagged Placed via MCP, so that tag tells you the trade came from the connector rather than from the MT5 terminal or another tool. If you notice an unexpected trade or a transaction you do not recognise, contact Axi Support promptly and review your MCP connection and trading permissions. While you wait, disconnect the connector or remove its trading permission so that no further chat instruction can become an order, and keep screenshots of the approval prompt and the trade history entry, because they show exactly what was approved and what was executed.

FAQ

Do I need a paid Claude plan to use the Axi MCP connector?

No. Axi states that the connector works on Claude’s Free plan as well as Pro, Max, Team, and Enterprise plans. The Free plan allows only one active custom connector at a time, so remove any other custom connector first or upgrade if you need several.

Can I connect an MT4 account to Claude with Axi MCP?

No. The connection requires an active MT5 account. Closed, archived, MT4-only, and Axi platform-only accounts can open the MCP settings page but cannot connect. Open or reactivate an MT5 account first, then return to the setup.

Does Claude trade automatically once it is connected?

No. Axi states that Claude is not an automated strategy or Expert Advisor, and it acts only when you ask it to. Trade actions require your explicit approval in the chat before they are sent, unless you yourself set a tool to Always allow in Claude’s permission settings.

How do I know if a trade was placed through Claude?

Check the Comment column of your trade history. Every trade executed through Claude is tagged Placed via MCP. If you see a trade you do not recognise, contact Axi Support promptly and review your MCP connection and trading permissions.

Is Claude’s advice through Axi MCP a trade recommendation?

No. Axi states that Claude is not a financial advisor and that its answers are not trade recommendations. AI-generated information can be inaccurate, incomplete, or outdated, so review every price, position figure, and order detail against MT5 itself before you approve anything.

Conclusion

Connecting Axi MT5 to Claude takes one hosted URL, one sign-in, and one careful permission review, and the verification that matters most costs nothing: a read-only balance question matched against MT5 itself. Keep trade approvals per action, test on demo before live, and use the Placed via MCP tag as your audit trail.

Frequently asked questions