TTMT – Telegram to MetaTrader

com.telegramtometatraderPublished by telegramtometatrader.comOfficial publisherv1.0.1Updated Oct 24, 2026

Read-only access to your own TTMT trading data: trades, signals, channels, performance and risk.

VerifiedStreamable HTTPWeb executableFinance

Overview

AI-generated overview

Read-only access to your own TTMT trading data, including trades, signals, channels, performance and risk.

What you can do
TTMT – Telegram to MetaTrader is a remote MCP server that exposes read-only access to a user's own TTMT trading data. According to the registry description, it covers trades, signals, channels, performance and risk. No individual tools are listed in the manifest, so the exact operations are not documented here.
When to use it
Worth considering if you already use TTMT to link Telegram signals to MetaTrader and want an assistant to review your trades, signals, channels, performance or risk. It is not useful without an existing TTMT account and data.
Requirements
A remote streamable HTTP endpoint at the provider's app host; no local package or runtime is declared. The manifest declares no authentication, environment variables or headers, so it is unclear what credentials, if any, are needed to reach your data.
Before you install
The manifest declares no authentication, which is unusual for a server exposing personal trading data; confirm with the provider how access is scoped to your account before connecting. The description says access is read-only, but no tool list is published to verify that. Trading data is sensitive financial information.

Installation

In SourceWeft

  1. Open TTMT – Telegram to MetaTrader in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.telegramtometatrader%2Fttmt/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "ttmt-telegram-to-metatrader": {
      "type": "http",
      "url": "https://app.telegramtometatrader.com/api/mcp/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

2
  1. v1.0.1LatestSep 22, 2026
  2. v1.0.0Sep 21, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.