Tracker report Telegram delivery MCP
Telegram Delivery MCP
A companion MCP server that takes a finished Yandex Tracker report and sends it to Telegram through an existing bot service
High risk
We rate an entry high when the tool writes to external systems, handles money, production databases or secrets, or runs arbitrary commands. The CLI installs it only with your consent.
Why this level
- The server triggers sending documents to Telegram on behalf of an existing bot
- It requires matching API keys for two external services; a leak of these would allow delivering arbitrary artifacts
Install
Manual install
docker compose up -d --buildRun inside a shared stack, with Tracker MCP and Telegram bot service addresses set in .env.
This is third-party code. Review the repository files before installing.
What it does
The server is built as a second, independent MCP for a training exercise on orchestrating multiple servers. It does not search Tracker issues itself: the agent first calls search, summarize and save-report on a separate YandexTrackerMCP server and gets an artifact_id, then calls send_tracker_artifact here. This server pulls the markdown document from Tracker MCP via an internal MCP client, hands it to an existing Telegram bot service, records the delivery in SQLite, and returns a delivery_id. Status can be checked with get_delivery_status, and recent attempts with list_recent_deliveries. The Telegram bot's own token is not needed here: the server talks to a protected internal endpoint of an already-deployed bot service.
Who it is for. For those already building or studying orchestration of several MCP servers around Yandex Tracker and existing Telegram bot infrastructure.
Good fit when
- You already run a separate YandexTrackerMCP server producing artifact_id
- You already have a working Telegram bot service with a protected internal endpoint
- You are studying the pattern of orchestrating several MCP servers in one scenario
Not a fit when
- You are looking for a standalone server that both reads Tracker issues and sends to Telegram itself: both pieces here are external and not part of this repository
- You have no ready Telegram bot service with the required internal API: without it send_tracker_artifact will not work
Example request
Find open critical issues in the AI queue, prepare a report and send it to TelegramLimitations
The server is useless on its own: it is designed to pair with an external YandexTrackerMCP (address set via TRACKER_MCP_URL) and an external Telegram bot service (TELEGRAM_BOT_SERVICE_URL), neither of which is part of this repository or documented as publicly available. It is built as a training project for a specific orchestration exercise, not as a general-purpose tool. The two services' API keys must match on both sides, or delivery will fail.
How to disable. Stop the telegram-delivery-mcp container or server process and remove it from the orchestration.
MCP
- Transport
- http
- Authentication
- API key
| Environment variables | |
|---|---|
| TRACKER_MCP_URL required | Address of the external YandexTrackerMCP server |
| TRACKER_MCP_API_KEY required, secret | Key matching MCP_API_KEY on the Tracker MCP side |
| TELEGRAM_BOT_SERVICE_URL required | Address of the existing Telegram bot service |
| TELEGRAM_BOT_SERVICE_API_KEY required, secret | Key matching BOT_SERVICE_API_KEY on the bot's side |
Security check
- The server triggers sending documents to Telegram on behalf of an existing bot
- It requires matching API keys for two external services; a leak of these would allow delivering arbitrary artifacts
README in short
The README describes the server as an independent second MCP for the 'Day 20. Orchestration MCP' training assignment, lists its four tools, explains that SQLite stores deliveries in data/deliveries.db, gives local run instructions via Python and Docker Compose, the address and key variables for the two external services, and an end-to-end verification scenario via a separate e2e script.
FAQ
Does this server need a Telegram bot token?
No, it calls a protected internal endpoint of an already-deployed bot service, not the Telegram Bot API directly.
Can the server find Tracker issues itself?
No, search and summarization happen on a separate YandexTrackerMCP server; this one only delivers the finished artifact.
Related
An MCP server with n8n node and template knowledge: the agent picks nodes, validates configs and, with API access, creates workflows in your n8n
Zapier's official MCP plugin: the agent gets actions across thousands of apps through your Zapier account
Awesome Claude Skills by Composio
Awesome Claude Skills
A curated list of Claude skills and plugins, plus Composio's own automation skills for 78 SaaS apps
A plugin and CLI catalog for agents: generates command-line interfaces for GUI apps like GIMP and Blender and installs ready ones via CLI-Hub