MCP Telegram

Created By
tacticlauncha year ago
A TypeScript implementation of an MCP (Model Context Protocol) server for working with Telegram through MTProto
Overview

what is MCP Telegram?

MCP Telegram is a TypeScript implementation of a Model Context Protocol (MCP) server designed for interacting with Telegram through the MTProto protocol, enabling AI models to communicate with Telegram.

how to use MCP Telegram?

To use MCP Telegram, install the dependencies, build the project, and run the server using CLI commands. You can sign in to Telegram, start the MCP server, and log out using the provided commands.

key features of MCP Telegram?

  • TypeScript implementation of MCP for Telegram
  • Supports stdio and SSE transports for real-time communication
  • CLI commands for easy interaction with Telegram
  • Integration with AI models like Claude

use cases of MCP Telegram?

  1. Building Telegram bots that utilize AI for responses.
  2. Creating applications that require real-time communication with Telegram users.
  3. Integrating Telegram functionalities into AI-driven platforms.

FAQ from MCP Telegram?

  • What is the Model Context Protocol (MCP)?

MCP is a protocol that allows for context-aware communication between applications and services.

  • Is MCP Telegram free to use?

Yes! MCP Telegram is open-source and free to use under the MIT License.

  • What are the transport options available?

MCP Telegram supports stdio and SSE transports for different integration needs.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
tacticlaunch
Star
0
Language
TypeScript
License
MIT license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago