"Telegram" matching MCP servers:

Enables remote execution of Codex CLI commands and provides an MCP tool for AI agents to escalate questions to humans via Telegram, allowing for human-in-the-loop workflows when away from the machine.

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.

This MCP server exposes a Telegram client that runs on the user's own account, enabling AI agents to read, search, send, and manage messages, press bot buttons, and work with chats, groups, and channels from the terminal. It is read-only by default, with writes requiring explicit human approval and every action logged for safety.

Zero-dependency MCP server to orchestrate a swarm of Claude Code / Codex sessions across WezTerm panes: any session can discover, spawn, prompt, and read the others via MCP tools. One session becomes the coordinator; crash isolation keeps peers alive; auto-handoff resumes sessions when context fills. Optional Telegram phone control.