TTMT Docs

Appearance

Connect with Other MCP Clients ​

The Model Context Protocol (MCP) is an open standard, not a Claude-only feature. TTMT exposes a remote MCP server, so any AI client that speaks the same protocol can connect to it — ask questions about your own trades, performance, settings, and risk status in plain language. You are not locked into a single vendor.

This page is for clients other than the ones with their own step-by-step guides. If you use Claude, start with the dedicated pages for claude.ai, Claude Desktop, or Claude Code instead — they are the same connection, just with exact menu paths.

Availability

MCP access is enabled per account by the TTMT team and is rolling out gradually. It uses the same account gate as the Power-User API — even after you sign in successfully, MCP only works once your account has API access turned on. If the connection or sign-in fails, enablement may still be in progress for your account. Message support at support@telegramtometatrader.com and we'll get you set up.

What "any MCP client" means ​

Two things make a client compatible with the TTMT MCP server:

  • Streamable HTTP transport. This is the modern MCP transport. The older SSE (Server-Sent Events) transport is not supported — the TTMT server has it disabled. If your client only offers a legacy "SSE" connection option, it cannot connect. Choose the Streamable HTTP (sometimes labelled "HTTP" or "remote MCP") option.
  • OAuth 2.1 sign-in. There is no separate MCP password or API key to paste. Your client signs you in with your TTMT account through a standard OAuth flow and you approve a consent screen. That's the whole handshake.

If a client advertises support for remote MCP servers over Streamable HTTP with OAuth, it should connect. We keep this vendor-neutral on purpose: we don't certify or endorse specific third-party products, and the exact wording of menus differs from one app to the next.

The connector URL ​

Point your client at this one address:

https://app.telegramtometatrader.com/api/mcp/mcp

That's the entire configuration — no host to fill in, no path to construct. Wherever your client asks for a "remote MCP server URL", "custom connector URL", or "server endpoint", paste that value.

The generic connection flow ​

Every compliant client walks the same three steps, whatever the labels look like in its interface:

  1. Add the remote MCP server URL. Find your client's option to add a custom or remote MCP connector and paste the connector URL above. Pick the Streamable HTTP transport if you're asked to choose a transport.
  2. Complete the OAuth sign-in. Your client opens a browser sign-in. Sign in with your TTMT account — the same login you use for the dashboard. There is no MCP-specific credential.
  3. Approve read-only access. A consent screen shows the client's name and the access it's requesting: read-only (ttmt:read). Approve it. Nothing is granted without this explicit approval.

Once approved, your client can call the tools. Every request is re-verified against your TTMT account — there are no long-lived sessions, so the connection stays tied to your live account access.

TIP

If sign-in and consent both succeed but tool calls still fail, the most likely cause is the availability gate above: your account may not have API access enabled yet. That's the same gate the Developer API and API keys use. Message support to confirm.

What you can ask ​

The server is strictly read-only. It can never place, modify, or close a trade, change a setting, move funds, or touch another user's data. Read-only means read-only — there is no write capability of any kind. What it gives your client is a set of tools that read and summarize your own data:

  • Accounts and positions — your connected MetaTrader accounts, their halt state, and your currently-open positions with total floating P&L.
  • Trades and signals — filtered, paginated trade history, single-trade deep dives, and parsed signals including the ones that were never traded (rejected, ignored, skipped).
  • Performance and digests — aggregated closed-trade performance (net P&L, win rate, profit factor) and one-call activity rollups for a period.
  • Settings, profiles, and channels — your effective settings, what each trading profile overrides, and which channels route to which accounts.
  • Risk and previews — per-account daily-loss-halt history, an advisory settings healthcheck, and a hypothetical order-plan preview (pure computation — no trade is ever placed).

For the full list of tools and the exact questions each one answers, see the Tool Reference.

Streamable HTTP only

The legacy SSE transport is disabled on the TTMT server. A client configured to use SSE will not connect. Use Streamable HTTP.

Rate limit ​

You get 60 requests per minute, counted per user and shared across every MCP client you connect. If two apps are talking to the server at once, they draw from the same budget.

One quirk to know: when you hit the limit, some clients show the throttled requests as a sign-in or authentication failure rather than an explicit "rate limited" message. If requests suddenly start failing after a burst of activity, wait a minute and try again before assuming the connection broke.