"telegram" matching MCP servers:

Enables Claude Code to send messages to and receive instructions from Telegram, with task tracking and persistent storage.

MCP server for delivering Yandex Tracker artifacts to Telegram via a bot service. It works in conjunction with YandexTrackerMCP to send summarized reports and verify delivery.

A read-only MCP server that syncs only the Telegram chats, folders, and forum topics you explicitly mark (via Telegram folders or watch.py) into a local SQLite index using Telethon, then exposes 13 read-only tools to an agent. Enables listing watched topics with unread counts, fetching new messages since last read, paging and date-filtered history retrieval with context budgets, full-text search over years of history (SQLite FTS5/bm25), activity stats, link/mention extraction, digests, and extracted entities such as tasks, decisions, promises, and questions with overdue tracking — all through user-defined aliases. No tool writes to Telegram, keeping the integration strictly read-only.

A Model Context Protocol server that uses Git as a backend for a collaborative todo system, enabling natural language interaction with Claude Desktop/Claude Code. It features a web-based Kanban board and Telegram bot for multi-interface todo management.

Automates task execution from Notion across GitHub, Instagram, VS Code, and Telegram, running as an MCP server locally or as a Vercel cron job.

Enables coding agents to maintain persistent project memory across sessions, manage tasks, and communicate with users via Telegram, including notifications and interactive approval requests.

An MCP server that enables agents to delegate asynchronous tasks to registered humans, with support for threaded conversation, result review, and delivery via web, email, or Telegram.