Axi MCP Is Live: Connect Claude to Your MT5 Account

Most of the MCP coverage in this corner of the internet is about do-it-yourself bridges: install a server, edit a config, hope it holds. This is the other direction. Axi has shipped its own. A hosted MCP server that connects your MT5 account to Claude, with no local software to install and no config file to edit.

It is live at mcp.axi.com. The soft launch began on 17 September 2026, starting with existing SVG (St. Vincent) clients on MT5 accounts. It is an early release, so treat the details below as the current state rather than a fixed contract.

Here is what it does, how to connect it in about a minute, and, because this is the part the press release will skip, what it does not solve.

What it actually is

A secure link between your MT5 account and Claude, authorised by you. You connect from the broker's side, paste the MCP URL into Claude, log in and approve. After that Claude reconnects automatically using the saved session.

The protocol is the same open Model Context Protocol that MetaTrader 5 added natively in its own terminal and that our earlier guides walked through building by hand. The difference here is who runs it: the broker, not you.

What you can do with it

The documentation groups it into five areas:

• Manage your accounts, trading accounts, account status, leverage, balance, equity and margin, read directly in the chat.
• Explore markets. Available symbols, live prices, spreads and historical candle data. Useful for sanity-checking an idea before you act on it rather than after.
• Monitor positions, open positions, current prices, unrealised P&L, stop loss and take profit.
• Manage trades, open, modify or close positions and place pending orders by describing what you want.
• Trading history, executed trades, entry and exit prices, commissions and deal details.

The example used in the launch material is a real order, long 0.1 lot of Gold, placed, filled and confirmed in plain English. That is the headline capability, and it is worth pausing on: this is not a read-only dashboard bolted onto a chatbot. It writes.

Connecting it

Eight steps, and none of them involve a terminal:

1. Go to Claude's connectors page at claude.ai/customize/connectors.
2. Click Add.
3. Name it Axi.
4. Enter the URL https://mcp.axi.com/mcp.
5. Continue with the default options and click Connect.
6. Log in to your Axi account and approve the connection.
7. Start using it.
8. Done, Claude reconnects automatically on future visits from the saved session.

One practical note that is easy to miss: custom connectors work on Claude's Free plan, not just Pro and above. Free accounts can hold one custom connector, so this can be that one at no cost. You would only need a paid plan if you want to run it alongside other custom connectors.

The approval model is the interesting part

This is where a broker-hosted server can do something a self-built bridge usually does not.

Your Axi login is not shared with Claude. The connection is encrypted, and any trade or order action requires your explicit approval in the chat before it goes through, including live trades. You can disconnect at any time, from Claude or from the broker.

Two details worth knowing as a matter of hygiene. First, trades placed through Claude MCP carry a distinct order comment, so a trade that arrived via the chat is identifiable afterwards in your history. Second, Claude is not a licensed adviser and its responses are not recommendations, the documentation is explicit about this, and it matches the position we have taken in every article on this site. The model summarises and reasons; the decision and the risk stay with you.

What "production-hardened" means here

The launch material includes the engineering detail, which is unusual and worth summarising because it addresses the obvious question: is a chatbot wired to an order ticket actually safe to use?

The MT5 gateway was load tested, production infrastructure was scaled afterwards, and a rate limiter was added for real client load. Then a structured test round was run across live and demo accounts with real execution: MT5 data fields verified against source, position reconciliation checked to the cent, and client confirmation requested before writes.

Read that alongside the approval requirement and the picture is a system designed on the assumption that the model will occasionally be wrong, which is the correct assumption. The reason to care about a reconciliation-to-the-cent test is that it is the check that catches the failure mode that actually hurts: your platform and your chat disagreeing about what you hold.

Availability and what is next

Today the scope is narrow and stated plainly:

• MT5 accounts only. MT4 is not covered.
• SVG clients first, as the initial rollout group.
• Two items in motion, no dates: assessing compliance readiness to open beyond SVG into regulated markets, and extending the capability beyond MT5 to ATP (Axi's own platform).

How this compares to MT5's own MCP server

MT5 Build 6060 added native MCP support and a built-in AI Assistant, which we covered in MetaTrader 5 Now Ships Its Own MCP Server. If you have read that piece, the trade-off here will look familiar.

• MT5's built-in server is an assistant bolted to the terminal. It runs on your machine, it is configured broker-side, and it is aimed at a human sitting in front of the platform.
• Axi MCP is hosted by the broker and consumed from a third-party assistant. Nothing to install, it works from Claude on desktop or web, and connection state is managed for you, but the tool surface and the guardrails are the broker's design, not yours.

If you need your own risk ceilings, your own instrument allow-list, or MT5 driven headlessly out of a Python pipeline, the answer is still a custom server, see our advanced guide. What has changed is that the entry level no longer requires building anything at all.

What it does not solve

Being clear about this, because a broker shipping AI access is easy to over-read.

• It is not an edge. Access to your own account data is table stakes. Deciding what to trade, when, and how much is untouched by this release.
• It does not analyse for you. Asking Claude to explain what you are seeing is useful. It is not a substitute for having a process.
• It does not backtest. Historical candles through the chat are for checking a chart, not for validating a strategy.
• It does not make the model right. A model that confidently misreads your exposure is still a model that confidently misreads your exposure. The approval gate is the control that matters, and it works precisely because it assumes that.
• It does not remove the demo. If anything, an assistant that can place real orders raises the value of rehearsing on a demo account first.

Bottom line

Two years ago, connecting an AI assistant to your trading account meant building the bridge yourself and owning every failure mode that came with it. Now there are two paths in, one from the platform vendor and one from the broker, and neither requires writing code.

That is genuinely useful, mostly for the boring half of the workflow: reading your own exposure quickly, pulling spreads and candles without alt-tabbing, and reviewing trade history in conversation instead of in a report. If trading conversationally is something you have been curious about but not curious enough to set up, this is the cheapest way to find out.

Just do not mistake a better interface for a better process. The interface is now the easy part.

Product details in this article are drawn from the Axi MCP technical documentation at mcp.axi.com and from Axi's launch announcement dated 18 September 2026. The server is in an early (soft-launch) state: capabilities, eligibility and regional availability may change. Always confirm current behaviour in the official documentation.