Ask Your AI Assistant About Your Trades, Read-Only

TTMT has a connector that lets an AI assistant such as Claude or ChatGPT read your own trading data and answer questions about it in plain language. You connect it once, sign in with your TTMT account, and then ask things like "why didn't my last EURUSD signal get traded?" The assistant fetches the record from your account and answers from it.

The connector only reads. It has no way to place a trade, change a setting, close a position, or move money. That limit is the first thing a trader should check before letting an AI near a live account, so a good part of this article is about where it sits.

What the connector is

The connector uses MCP, the Model Context Protocol, which is an open standard for plugging an AI app into an outside source of data. Without it, you would be exporting trades and pasting numbers into a chat window. With it, the assistant asks TTMT for the specific slice it needs and works from that.

Because the standard is open, the same connector works in more than one app. The docs carry a setup page for claude.ai, Claude Desktop, Claude Code, ChatGPT (through its developer-mode connectors), and any other client that supports the modern connector transport and sign-in. You can connect it in two apps at once. They read the same data.

What the assistant gets is a fixed set of 20 read-only tools. Each one fetches one kind of thing: your accounts, a list of trades, one trade in detail, your open positions, performance figures, your settings, your channels, your signals, your risk status. You never call a tool by name. You ask a normal question and the assistant picks the tool, or chains several.

What you can ask it

The useful questions fall into a few groups. These examples come from the connector's own documentation.

The daily check. "Give me my morning trading summary" returns closed P&L (profit and loss), open positions, any halted accounts, skipped signals, and your best and worst channel for the period, in one answer. "Which of my accounts are halted right now?" and "Is the market open right now?" are the two I would reach for when nothing seems to be trading.

One trade, in detail. Every trade has a reference such as trd_abc123. "Walk me through what happened on trade trd_abc123" pulls the signal, its positions and orders, and a reconstructed timeline. This is the same record behind the trade view built for auditing, read aloud. It also includes where each executed price came from, which is the labeling described in every price in your trade says where it came from. If the timeline does not explain why something happened, ask "why did trd_abc123 only fill 2 of 4 layers?" and the assistant can go to the step-by-step engine trace for that trade. A layer is one of the staggered entries TTMT splits a trade into.

Signals that never became trades. The connector lists parsed signals including the ones that were rejected, ignored, or skipped. "Why didn't my last EURUSD signal get traded?" gets a one-call explanation: the signal's status, the channel's routing, any risk halt around that time, and the trace when one is available.

Performance and channel results. "How does my Aggressive profile compare to Balanced last month?" or "Which of my channels made the most money this quarter?" Performance can be grouped by account, channel, profile, symbol, or month, and covers net P&L, win rate, profit factor, and average realized R (the result measured in multiples of what the trade risked). There are separate tools for drawdown and streaks, and for when you trade best by weekday, hour, or session.

Open risk right now. "What's my total floating P&L right now?" and "How exposed am I to the US dollar across all my open trades?" The exposure answer breaks open positions down by currency and warns when too much sits on one leg.

Settings. "What settings apply when this channel's signals hit my live account?" resolves your effective settings and names which layer supplied each field, your base settings or a channel-bound profile.

Guided prompts

If you would prefer not to compose the question, the connector ships seven guided prompts that most clients show as slash commands. They cover a morning review, a settings healthcheck, a channel deep-dive, a risk review, a weekly report, a drawdown postmortem, and a channel vetting. The two channel prompts end in a keep, watch, or drop verdict and are written to say so when the trade count is too small to be confident. The settings healthcheck is advisory pattern-matching on your own recent history. The docs are explicit that it is never a backtest.

Order-plan previews

One question looks like an action and is a calculation: "If I got a XAUUSD BUY signal now, what would my order plan look like?" TTMT computes the order plan the platform would produce for that hypothetical signal under your current settings, or under a profile you name. Nothing is sent to your broker and no order is created.

What it can never do

There is no write tool in the connector at all. It cannot place a trade, modify one, close a position, cancel an order, change a setting, or move funds. This is how it is built, so there is no instruction you or the assistant can give that turns it into something that acts.

Two practical consequences follow. Any suggestion the assistant makes about your settings is yours to apply by hand in the dashboard. And if an assistant ever tells you it "placed" or "closed" a trade through the connector, it is wrong. It cannot.

It also cannot see anyone else's data. Every request is signed in as you and re-checked on the server, so the connector only reaches the account you signed in with.

How access and security work

You do not create a password or an API key for the connector, and you never paste a secret into your AI client. The flow is five steps:

1. You add the connector URL in your AI client.
2. The client opens a TTMT sign-in page.
3. You sign in with your normal TTMT account.
4. A consent screen names the app asking for access and the read-only permission it wants, and you approve it.
5. You are connected.

The sign-in runs on OAuth, the same standard behind "Sign in with..." buttons across the web. Access is verified on every single request, so there is no long-lived session sitting open in the background. You can disconnect whenever you like from your AI client's own connector settings. The next request is then rejected, and TTMT does not reconnect a connector you removed.

One thing sits outside our control. Whatever the assistant reads, your AI client receives, and that client's own data-handling policy applies to it. Choose the assistant with that in mind.

None of this touches your broker login, which is handled separately and described in your broker password never reaches us.

Who can use it today

Access is set per account. The docs say it depends on your account's enablement and the subscription-access rollout, and that a valid sign-in alone does not establish access. The current rule is on the docs' account access section, next to the usage limits, which vary by plan. If sign-in or consent fails, message support and we will check your access.

The overview is on the connector page, and the MCP docs walk through setup for each client. Start a free 7-day trial at telegramtometatrader.com.