TTMT – Telegram to MetaTrader is the official remote MCP server from telegramtometatrader.com. It answers at https://app.telegramtometatrader.com/api/mcp/mcp over streamable HTTP and asks you to sign in with your telegramtometatrader.com account before it lists its tools, so your client opens a login the first time it connects. Our probes reached it 4 of 4 times since 23 September 2026; the last check, on 7 November 2026, got the sign-in challenge, so it is up.
Read-only access to your own TTMT trading data: trades, signals, channels, performance and risk.
Description as the publisher wrote it.
A sign-in. The server refused to list its tools to an anonymous client and answered with an authentication challenge, which is how an MCP server protected by OAuth behaves. Add it with one of the setups below; the first connection opens a login for your telegramtometatrader.com account, and the tools appear once you have approved it.
Every block below points at https://app.telegramtometatrader.com/api/mcp/mcp. Pick your client and copy.
claude mcp add --transport http ttmt-telegram-to-metatrader https://app.telegramtometatrader.com/api/mcp/mcp
{
"mcpServers": {
"ttmt-telegram-to-metatrader": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://app.telegramtometatrader.com/api/mcp/mcp"]
}
}
}{
"mcpServers": {
"ttmt-telegram-to-metatrader": {
"url": "https://app.telegramtometatrader.com/api/mcp/mcp"
}
}
}{
"servers": {
"ttmt-telegram-to-metatrader": {
"type": "http",
"url": "https://app.telegramtometatrader.com/api/mcp/mcp"
}
}
}{
"context_servers": {
"ttmt-telegram-to-metatrader": {
"url": "https://app.telegramtometatrader.com/api/mcp/mcp"
}
}
}{
"mcpServers": {
"ttmt-telegram-to-metatrader": {
"serverUrl": "https://app.telegramtometatrader.com/api/mcp/mcp"
}
}
}{
"mcpServers": {
"ttmt-telegram-to-metatrader": {
"url": "https://app.telegramtometatrader.com/api/mcp/mcp"
}
}
}name: TTMT – Telegram to MetaTrader
version: 0.0.1
schema: v1
mcpServers:
- name: TTMT – Telegram to MetaTrader
type: streamable-http
url: https://app.telegramtometatrader.com/api/mcp/mcp{
"mcpServers": {
"ttmt-telegram-to-metatrader": {
"httpUrl": "https://app.telegramtometatrader.com/api/mcp/mcp"
}
}
}{
"mcpServers": {
"ttmt-telegram-to-metatrader": {
"type": "http",
"url": "https://app.telegramtometatrader.com/api/mcp/mcp"
}
}
}{
"mcpServers": {
"ttmt-telegram-to-metatrader": {
"url": "https://app.telegramtometatrader.com/api/mcp/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fapp.telegramtometatrader.com%2Fapi%2Fmcp%2Fmcp&type=streamable_http&id=ttmt-telegram-to-metatrader&name=TTMT%20%E2%80%93%20Telegram%20to%20MetaTrader
It answered our last check on 7 November 2026 in 91 ms. Over 4 checks since 23 September 2026 it answered 4. Status here comes from Neuronto's own probes, not from the publisher.
Yes. It is published by telegramtometatrader.com and served from app.telegramtometatrader.com, the vendor's own domain: https://app.telegramtometatrader.com/api/mcp/mcp.
Add the server with a setup above. The first time your client connects it opens the sign-in page for telegramtometatrader.com; approve it and the tools load.
It answered our last check on 7 November 2026 in 91 ms. Over 4 checks since 23 September 2026 it answered 4.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://app.telegramtometatrader.com/api/mcp/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It needs a sign-in rather than a key you paste: the server answered with an authentication challenge, so your client runs the login when it first connects.
Publisher: com.telegramtometatrader. Endpoint host: app.telegramtometatrader.com. ARD identifier: urn:air:com.telegramtometatrader:mcp:ttmt.
First indexed 21 September 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.