--- url: /mcp/clients/chatgpt.md description: >- Add the TTMT connector to ChatGPT using developer mode so ChatGPT can answer read-only questions about your own trading data. --- # Connect with ChatGPT You are not limited to Claude. MCP is an open standard, and ChatGPT can connect to the same TTMT connector — the same URL, the same TTMT sign-in, the same read-only access. Once it is connected, you can ask ChatGPT about your own trades, positions, performance, settings, channels, and risk status without exporting anything or pasting numbers into the chat. ChatGPT reaches TTMT through a **read-only connector**. It can read your data to answer your questions, but it can never place, modify, or close a trade, change a setting, move funds, or see anyone else's data. There is no write access to switch on. ::: info Availability Two things have to line up. On the TTMT side, MCP access depends on account enablement and the subscription-access rollout — see [Account access](/mcp/security#account-access). On the OpenAI side, custom MCP connectors live behind ChatGPT's **developer mode**, which OpenAI documents for Plus, Pro, Business, Enterprise, and Edu accounts on the web, subject to your workspace policy. If sign-in or consent fails, [message support](mailto:support@telegramtometatrader.com) to check your TTMT access. ::: ## Before you start You need: * **A ChatGPT account on a plan that offers developer mode** — OpenAI documents it for Plus, Pro, Business, Enterprise, and Edu on the web. It is not available on the free tier, and on Business or Enterprise an admin may have to allow it for the workspace first. If the toggle is missing entirely, that is almost always why. * **A TTMT account** at [app.telegramtometatrader.com](https://app.telegramtometatrader.com) with MCP access (see availability above). You do **not** need an API key, a separate MCP password, or anything pasted from your TTMT settings. You sign in with your normal TTMT account and approve a consent screen. ## The connector URL This is the only value you copy into ChatGPT: ``` https://app.telegramtometatrader.com/api/mcp/mcp ``` The `/mcp` path at the end matters — it is the server endpoint, not a website address. Paste it exactly. ## Setup steps 1. **Turn on developer mode.** In ChatGPT, open **Settings → Security and login** and enable **Developer mode**. 2. **Start a new connection.** Open ChatGPT's plugins area and choose the **+** (add) option to create a connection to a remote MCP server. 3. **Name it.** Give it a name and description you will recognise later — `TTMT` and "my trading data, read-only" are plenty. 4. **Point it at TTMT.** Choose the public HTTPS endpoint option and paste the connector URL above, `/mcp` path included. 5. **Sign in with your TTMT account.** ChatGPT opens a TTMT sign-in window — the same email and password you use for the dashboard. 6. **Approve read-only access.** On the consent screen, review what is being granted — read-only (`ttmt:read`) — and click **Allow**. 7. **Check the tools it found.** ChatGPT lists the tools it discovered from the server. Seeing that list is how you know the connection genuinely completed rather than merely saving. ::: tip OpenAI moves this menu from time to time Developer mode is OpenAI's surface, not ours, and the exact menu path has changed more than once. If a label above does not match what you see, OpenAI's own [connect-and-test guide](https://developers.openai.com/plugins/deploy/connect-chatgpt) carries the current path. Nothing on the TTMT side changes — the connector URL and the sign-in are the same either way. ::: ## Using it in a chat A newly created developer-mode connection lands in your **drafts**, and it is not automatically live in every conversation. Two things are worth knowing: * **Enable it for the chat.** Turn the TTMT connection on from the conversation's tools menu, then ask your question. If ChatGPT answers about your trading in general terms rather than *your* numbers, it almost certainly did not have the connector switched on. * **Refresh after we ship new tools.** ChatGPT caches the tool list it discovered at connection time. If a new TTMT capability does not show up, open the connection's details page and refresh it to re-fetch the tools from the server. You can also toggle individual tools on and off from that details page, which is handy if you want ChatGPT to read your performance but never your settings, for example. ## What you can ask Once connected, ask in plain language. A few examples: * "Give me my morning trading summary." * "Show me my losing `XAUUSD` trades this week." * "What's my total floating P\&L right now?" * "Which of my accounts are halted right now?" * "Why didn't my last `EURUSD` signal get traded?" * "If I got a `XAUUSD` `BUY` signal right now, what would my order plan look like?" The last one is a *preview* — a calculation of the order plan your current settings would produce for a hypothetical signal. No trade is placed. See the [tool catalog](/mcp/tools) for everything the connector can answer. ## About developer mode's risk warning ChatGPT shows a prominent warning when you enable developer mode, and it is worth understanding rather than clicking past. The warning exists because MCP connectors *in general* can expose write actions — a connector that deletes files or sends money is possible, and a model mistake or a prompt injection could trigger one. **The TTMT connector has no write tools at all.** It cannot place, modify, or close a trade, change a setting, or move funds, because those tools do not exist in it. That is a structural property of the server, not a permission you granted or could accidentally widen. See [Security & Access](/mcp/security) for how that is enforced on every request. The warning still applies to *other* connectors, though. Add remote MCP servers you trust, and check the URL you are pasting — for TTMT, that is `https://app.telegramtometatrader.com/api/mcp/mcp` and nothing else. ::: warning One budget across every assistant The **60 tool calls per minute** rate limit and the Essential plan's **daily tool-call allowance** are counted per TTMT user, not per app. If you have TTMT connected in both ChatGPT and Claude, they draw from the same budget. See [Daily limits by plan](/mcp/security#daily-limits-by-plan). ::: ## If the connection fails | What you see | What to do | |:---|:---| | **No developer mode toggle** | Check your ChatGPT plan, and on Business or Enterprise ask your workspace admin whether it is allowed. | | **The connection saves but no tools appear** | Open the connection's details page and refresh it. A cached or partial discovery is the usual cause. | | **Sign-in or consent won't complete** | Check the URL character for character, then [message support](mailto:support@telegramtometatrader.com) to confirm your TTMT MCP access. | | **It connected, but it isn't used in the chat** | Enable the TTMT connection from the conversation's tools menu — a draft connection is not on by default. | | **A "per-minute limit" message** | You have reached 60 tool calls in a minute. You stay signed in. Wait up to a minute and ask again — see [Troubleshooting](/mcp/troubleshooting). | | **A friendly "daily limit" message** | That is the Essential plan's daily allowance, reset at midnight UTC. Pro and above are unlimited. | ## How to disconnect Delete the connection in ChatGPT's connection settings. Access stops immediately: every TTMT request is re-verified, and there is no long-lived session left on our side to expire. TTMT never initiates the disconnect — the connection is yours to remove whenever you want. ## Related pages * [MCP overview](/mcp/) — what the connector is and why you'd use it * [MCP quickstart](/mcp/quickstart) — the short version, for any client * [Tool catalog](/mcp/tools) — every read-only tool and the questions it answers * [Security & Access](/mcp/security) — sign-in, permissions, and per-account isolation * [Connect with claude.ai](/mcp/clients/claude-ai) * [Connect other MCP clients](/mcp/clients/other-clients)