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

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

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.

Deploys a remote MCP server on Cloudflare Workers without authentication, enabling custom tool integration and connection to AI Playground or Claude Desktop.

Enables AI agents to manage Telegram chats, messages, contacts, users, groups, and channels via 50+ MCP tools, with a reactive inbox and per-topic proxy isolation for multi-agent setups.

A general-purpose MCP gateway integrating tool management, memory, reminders, and multi-channel messaging (Telegram/QQ), enabling autonomous AI agents.

A universal agent gateway that integrates MCP tools (memory, reminders, web search, email, calendar, etc.) with multi-channel messaging (Telegram, QQ) and a heartbeat system for autonomous life simulation.

A local MCP server that enables direct, persistent communication between multiple Claude Code agent sessions through a secure messaging channel. It includes built-in guardrails to manage message exchanges and supports optional human monitoring via Telegram.

A custom Model Context Protocol server that provides real-time financial analysis tools including stock monitoring, portfolio management, market summaries, and automated price alerts with Telegram notifications.

Provides Claude Desktop and Cursor with full access to the ofshore.dev ecosystem, including system health, AI research, build pipelines, knowledge bus, Telegram messaging, and SQL queries.

A self-hostable, multi-MCP personal-assistant framework with multi-provider LLM orchestration, a real safety model, and a production-grade test suite. Nexus Core is the engine behind a Telegram-based personal assistant: it takes a message (text or voice), routes it through an LLM, lets the model call tools exposed by a fleet of Model Context Protocol servers, gates anything destructive behind exp

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.