TTMT Docs

Appearance

MCP Troubleshooting & FAQ ​

Most MCP problems come down to one of three things: your account not being enabled yet, the 60-per-minute rate limit, or a client that doesn't speak the right transport. This page walks each one, then answers the questions people ask most often.

If you haven't connected yet, start with the MCP Quickstart. For how access is scoped and verified, see MCP Security.

You pasted the connector URL, but the sign-in never appears, the consent screen errors, or the client reports a connection failure.

Account access is one possible cause. MCP checks its own access policy, which can admit an explicit account grant or eligible subscription status when that rollout is enabled. It is not identical to the Developer API gate. A generic connection failure can also come from an expired token, incomplete consent, rate limiting or client incompatibility; it does not establish the cause by itself.

Availability

MCP access is enabled per account by the TTMT team and is rolling out gradually. If sign-in or the consent step fails, your account may simply still be getting enabled. Message support and we'll confirm your status and switch it on.

Before you assume it's the gate, rule out the quick things:

  • Check the URL exactly. The connector URL is https://app.telegramtometatrader.com/api/mcp/mcp. A trailing slash, a typo, or an old address will fail.
  • Sign in with your TTMT account — the same email and password you use at app.telegramtometatrader.com. There is no separate MCP password or API key.
  • Approve the consent screen. After sign-in, your client shows a consent step asking to grant read-only (ttmt:read) access. Nothing connects until you click Allow. If you dismissed it, remove the connector and add it again to re-trigger the prompt.
  • Use a supported client. See Which clients work? below — a client that can't do Streamable HTTP with OAuth 2.1 will never complete the handshake.

If the URL is right, you're signing in with the correct account, and it still fails, that points to the access gate. Message support at [email protected] and we'll check whether your account is enabled.

I connected fine, but I get errors after a while ​

You were asking questions happily, then requests started failing — often looking like a sign-in or authentication error out of nowhere.

The usual cause is the rate limit: 60 requests per minute per user, shared across every MCP client you have connected. A busy back-and-forth — especially one where your assistant fans out several tool calls to answer a single question — can burn through that budget faster than you'd expect.

A quirk to know about

When you hit the rate limit, requests can briefly surface as an authentication failure rather than an explicit "too many requests" error. This is a known client-facing quirk. If things were working a moment ago and then started failing under heavy use, it's almost always the rate limit, not your login.

What to do:

  • Wait a minute, then continue. The limit resets on a rolling one-minute window, so pausing clears it.
  • Slow the pace. Ask one focused question at a time instead of firing several in quick succession.
  • Remember the budget is shared. If you've connected the same account from claude.ai and ChatGPT at once, both draw from the same 60/minute.

If failures persist even after you've slowed down and waited, treat it like a connection problem — see the section above — and reach out to support.

I got a message about a daily limit ​

You were asking questions fine, and then your assistant relayed a message saying you'd reached your daily MCP limit, suggesting you wait until tomorrow or upgrade.

That's the Essential-plan daily allowance, which is separate from the per-minute rate limit above. On the Essential plan the connector allows about 25 tool calls a day (roughly three questions), reset at midnight UTC. It's a soft, friendly stop — not an error, and not a sign anything is broken.

You have two options:

  • Wait for the reset. Your allowance refills at midnight UTC — come back and continue.
  • Upgrade to Pro for unlimited MCP usage. Pro also includes up to 5 MetaTrader accounts and advanced stats for comparing strategies. Upgrade from your billing settings.

Pro and higher plans have no daily cap. See Daily limits by plan for the full breakdown.

Daily limit vs per-minute limit

Two different limits can stop you, and they look different. The per-minute limit (60/min) tends to surface as a vague sign-in or authorization error after a rapid burst, and clears within a minute. The daily limit surfaces as a clear, plain-language "you've reached your daily limit" message with an upgrade suggestion, and clears at midnight UTC. If you got a friendly limit-and-upgrade message, it's the daily one.

Can Claude or ChatGPT place trades for me? ​

No. The MCP connection is strictly read-only. Your assistant can read your trades, positions, performance, settings, and risk status — it can never place, modify, or close a trade, change a setting, move funds, or touch anything.

Read-only, always

There is no trading tool. There is no write access. The MCP server cannot execute, cancel, or adjust orders, and it never will through this connection. Even a tool like preview_execution — which shows the exact order plan a hypothetical signal would produce — is pure calculation with no trade placed. If you want to change how TTMT trades, you do that yourself in your dashboard settings.

This is a deliberate safety boundary, not a temporary limitation. For the full picture of what the connection can and can't reach, see MCP Security.

Which clients work? ​

Anything that speaks the modern MCP transport. Concretely:

  • claude.ai — add it under Settings → Connectors → Add custom connector.
  • Claude Desktop — same path, Settings → Connectors → Add custom connector.
  • Claude Code — add it from your terminal:
bash
claude mcp add --transport http ttmt https://app.telegramtometatrader.com/api/mcp/mcp
  • ChatGPT — enable developer mode in ChatGPT's settings, then add the connector URL as a remote MCP server. Full steps: Connect with ChatGPT.
  • Any other MCP client that supports Streamable HTTP and OAuth 2.1. Point it at the connector URL and it will walk you through sign-in and consent.

The one thing that won't work is a client that only supports the legacy SSE transport — that transport is disabled on the TTMT server. If your client can't do Streamable HTTP with OAuth 2.1, it can't connect.

Connector URL

The URL is the same for every client: https://app.telegramtometatrader.com/api/mcp/mcp

I'm on ChatGPT and something's off ​

ChatGPT has three failure modes the Claude apps don't, and none of them are a TTMT problem:

  • There's no developer mode toggle. Custom MCP connectors are a developer-mode feature, which OpenAI documents for Plus, Pro, Business, Enterprise, and Edu accounts on the web. On Business or Enterprise, an admin may need to allow it for the workspace first.
  • It connected, but ChatGPT answers about trading in general instead of your account. The connection is probably not switched on for that conversation — a newly added one starts as a draft. Enable TTMT from the chat's tools menu and ask again.
  • A tool you read about isn't there. ChatGPT caches the tool list from when you connected. Open the connection's details page and refresh it to re-fetch from the server.

Full walkthrough: Connect with ChatGPT.

How do I disconnect? ​

You control the connection entirely from your own client — TTMT never initiates a disconnect. To remove it, delete the connector wherever you added it:

  • claude.ai / Claude Desktop — open Settings → Connectors, find the TTMT connector, and remove it.
  • Claude Code — run claude mcp remove ttmt in your terminal.
  • ChatGPT — delete the TTMT connection from ChatGPT's connection settings.
  • Other MCP clients — remove the connector in that client's settings.

Once removed, the client stops holding access. Because every request is re-verified and there are no long-lived server-side sessions, there's nothing lingering on TTMT's side to clean up.

Is my data shared with other users? ​

No. Every MCP request is scoped to your account and your account only. Your assistant sees your trades, your positions, your settings — never anyone else's. There is no shared view, no cross-account access, and no way for the connection to reach another user's data. See MCP Security for how that isolation is enforced on every single request.

Do I need a separate password or API key for MCP? ​

No. MCP authenticates through your existing TTMT account using OAuth 2.1. You approve read-only consent; unlike the separately gated Developer API, there is no API key to create or paste. Never paste an LSE key into your chat either.

Candles, replay or charts are unavailable ​

The market-analysis extension is experimental and separately gated. If get_price_history, replay_history and show_analysis are absent from your client’s tool list, use the recorded-data tools; connection success does not enable replay.

If tools are listed but fail, inspect the returned reason: provider access, unsupported symbol, missing historical inputs, partial coverage and an expired analysis need different responses. A smaller window may help a budget error, but cannot repair missing evidence. An unavailable result needs a new analysis, not a silent refresh of its old identifier.

If only the chart is missing, your client may not support the optional MCP App. Ask for the summary, tables, recorded trace, simulated events or bounded CSV instead. Text and visualizations use the same result.

Still stuck? ​

If none of the above resolves it, message support at [email protected]. It helps to include which client you're using (claude.ai, Claude Desktop, Claude Code, ChatGPT, or another), the exact error text your client shows, and roughly when it started.