"telegram" matching MCP servers:

MCP Server for Telegram

A bridge allowing Claude Desktop to access Telegram chats and messages via the Model Context Protocol, providing read-only capabilities to retrieve dialogs and messages from Telegram.

A stdio MCP server that lets Grok Bot receive spooled Telegram updates and respond through Telegram — listing and acknowledging pending messages, sending or editing replies, and showing editable progress drafts. It also exposes webhook helpers so the bot can manage its Telegram webhook configuration.

MCP server that exposes a Telegram bot over stdio transport, enabling LLM agents to discover each other, announce capabilities, and communicate via messages in shared group chats. It provides tools like whoami, announce, list_agents, ping_agent, send_message, list_chats, get_recent_messages, and wait_for_reply.

Enables running Claude Code around the clock through Telegram, with voice notes exchanged in both directions, a self-healing daemon that keeps sessions alive, memory and history preserved across restarts, and a live view of every tool call as it happens.

Enables running Claude Code continuously from Telegram with two-way voice notes, persistent memory, live tool-call progress, scheduled reminders, calendar access, and automatic daemon recovery. It also supports inline-button questions, group/forum threading, model routing, and a Mini App board for monitoring sessions, subagents, and token usage.

Enables users to operate Claude Code from Telegram around the clock, with two-way voice messages, persistent memory across restarts, and live visibility into every tool call through a self-healing daemon.

Enables users to run Claude Code from Telegram with two-way voice notes, persistent memory across restarts, scheduled reminders, Google Calendar, and live monitoring of agent sessions and tool calls.

Enables running Claude Code around the clock through Telegram, with two-way voice notes, persistent memory and history across restarts, scheduled messages, calendar access, and a live view of every tool call while Claude works. It ships as a self-healing daemon that installs in one line and keeps your existing bot and pairing intact.

Runs coding sessions around the clock from Telegram chat, with two-way voice notes, persistent memory across restarts, scheduled reminders, calendar access, and inline-button prompts. Streams live progress for every tool call so users can watch subagents, token usage, and session state as work happens.

Enables users to run Claude Code from Telegram with voice notes both ways, persistent memory, live tool-call progress, and 24/7 daemon supervision. It also adds scheduled messages, Google Calendar integration, inline buttons, and session/subagent monitoring.

Enables controlling and monitoring Claude Code sessions entirely from Telegram, with two-way voice messages, live visibility into every tool call, conversation memory that survives restarts, inline-button prompts, scheduled reminders, and Google Calendar access. A self-healing daemon with an auto-restart supervisor keeps the bot running 24/7 with zero downtime.

Enables users to drive Claude Code 24/7 from Telegram with two-way voice notes, persistent cross-restart memory, scheduled reminders and calendar access, and live visibility into every tool call via Agentic Mode and an Agents Board Mini App.

Enables running and managing Claude Code from Telegram with two-way voice messages, persistent memory across restarts, scheduled messages, calendar access, and live tool-call visibility through Agentic Mode. It also provides a self-healing daemon and an Agents Board for monitoring sessions, subagents, and token usage.

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).

An MCP server that lets coding agents like Cursor and Claude manage neural employees (AI assistants) across channels such as Telegram, WhatsApp, and web widgets. It provides tools for surveys, tasks, worker card management, Telegram bot control, and booking CRM.

Self-hosted workflow automation platform with a built-in MCP server. Lets AI agents build, validate, publish and run automations, and call any of its 238 integrations (Slack, Telegram, Google Sheets, Notion, ...) as tools.

A plug-in layer for AI coding agents that adds remote access via Telegram, self-evolving tool generation, agent-to-agent communication, session capture/replay, and semantic memory through MCP servers.

Enables MCP clients to retrieve Telegram setup plans, normalize task briefs, and run health diagnostics locally without exposing shell access or stored credentials.