"telegram" matching MCP servers:

https://github.com/EncryptMan/telegram-mcp

Connects Claude to your personal Telegram and Slack accounts, letting it read real DMs, groups, channels, unread messages, and search chats, with optional sending enabled by the user.

Enables MCP-compatible clients to securely access and manage Telegram accounts, chats, messages, media, and contacts, with tiered permissions, write controls, and local caching.

Enables AI agents to access and search Telegram conversations, including transcribed voice messages and OCR'd images, and to draft messages that require user approval before sending.

Enables remote control of the Cursor AI agent via chat platforms like GitHub Issues or Telegram, allowing users to start sessions and receive summaries and prompts in a chat thread.

Human-in-the-loop approval inbox for AI agents: an agent proposes an action (send email, post comment, run a command), a human approves, rejects, or edits it from a web, mobile, or Slack/Discord/Telegram inbox, and the agent only runs on approval. Full audit trail, self-hostable (MIT).

Mandatory human approval gate for autonomous AI agents. Before any critical, irreversible, or financially significant action executes — file deletion, production deployment, financial transaction — the agent calls oracle_validate. A human receives a real-time Telegram notification with full context and taps Approve or Reject. The agent waits for the decision before proceeding.

Human approval for AI agents: request_human_approval pauses a high-stakes action until a named person approves or rejects (console, email, Telegram, Slack); silence is not consent. Every decision is sealed in a hash-chained audit log. EU-hosted.

Schedule and manage social media posts across 13 platforms (Bluesky, Threads, Instagram, LinkedIn, Mastodon, YouTube, Facebook, Pinterest, Telegram, Nostr, X/Twitter, Discord, Tumblr and more). OAuth 2.0 + PKCE, 10 tools, draft-first workflow for AI agents.

Search your data exports from Google, Telegram, Spotify, and Instagram in one place. Everything runs on your own computer. Hybrid search and MCP, built in .NET 10

MTProto Telegram client for the terminal (Rust): a CLI for messages, media and contacts, an MCP server that pushes server-to-client notifications when new messages land (per-chat filtering), and an SSE stream. Local-first, no third-party APIs, single binary, MIT.

Read-only public Telegram group statistics from Limzo: search tracked communities and pull leaderboards, activity trends, member levels, and network-wide totals. No API key or account needed.

The watchdog for unattended AI agents: flags MISSED, FAILED, NO_EVIDENCE, RETRY_STORM, BUDGET, DRIFT and STALLED runs of Claude Code routines, OpenClaw, n8n and cron jobs, and alerts via Telegram, Slack or webhook. MIT and self-hostable.

MCP server for buying advertising outcomes such as Telegram subscribers and website traffic from a prepaid balance. Provides tools for campaign management, forecasting, and budget control, with guardrails so agents can spend but not fund or withdraw.

Local-first MCP server that puts your own LINE and Telegram chats behind one data layer — a daemon on your machine logs in with your own account, stores messages to JSONL + SQLite/FTS5, and exposes 6 MCP tools over streamable HTTP on 127.0.0.1. Not a hosted service and not an npx one-liner: you clone the repo, run the daemon, and log in yourself.

MCP server that exposes a Telegram user account over HTTP, enabling message sending, dialog listing, history retrieval, and message search via tools like send_message and list_dialogs.