"Telegram messaging platform" matching MCP servers:

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 for Telegram

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

Enables local, event-driven messaging between multiple AI coding-agent sessions on the same machine using only Node.js and the filesystem, allowing them to hand off tasks, exchange replies, and broadcast announcements without external infrastructure.

Local inter-agent messaging for AI coding agents via filesystem relay.

A FastMCP server for Cursor platform APIs enabling spend guardrails, cloud agent monitoring, and inter-agent inbox messaging.

Exposes pi as a sub-agent for MCP-capable coding assistants, enabling task dispatch, messaging, and interactive dialog handling via tools like pi_dispatch, pi_send, and pi_respond.

An MCP server that gives agents access to a network of 435 specialist agents and peer-to-peer A2A messaging, enabling keyless, real-time data queries and direct communication with other agents.

Let's your agent access the heroku platform

MCP server for AI-to-AI messaging on the AInternet with TIBET provenance. Enables sending, receiving, and resolving messages between AI agents using .aint domains.

Enables AI agents to delegate scoped tasks across multiple providers like Codex, Claude Code, and Antigravity through a single local MCP server, with quota monitoring, notifications, and remote control via messaging apps.

Enables local messaging between Claude Code, Codex, Pi, and other coding-agent sessions on the same machine, allowing them to discover each other, send updates, ask questions, and reply.

MCP server for multi-agent AI systems providing mailbox messaging, A2A task delegation, resource coordination, and a web dashboard.

Orchestrates multiple Claude Code agents across iTerm2 sessions with process-level isolation, enabling collaborative AI development workflows on multiple codebases with task-based inter-agent communication and persistent state management.

MCP server that exposes intercom tools inside Codex sessions, enabling discovery and messaging with other local coding agents (Pi, Claude Code, OpenCode) through a shared broker.

MCP server that integrates OpenClaw AI assistant with Claude Code, enabling chat, task management, messaging, memory, alerts, agent spawning, and web search through configurable tools.

Enables interaction with the AGNTCY multi-agent network through MCP, providing tools for agent registration, discovery, and messaging using ACP and SLIM protocols.

In-memory MCP server for cooperative collaboration between separate agents, enabling topic-based messaging and coordination via tools like create_topic, join_topic, send_message, read_messages, and check_in.