MCP Telegram Server

Created By
leshchenko1979a year ago
Telegram MCP Server - now you can talk to your Telegram from Cursor
Overview

What is MCP Telegram Server?

MCP Telegram Server is a powerful implementation that allows users to interact with Telegram through a clean API interface, enabling functionalities such as message search, sending, and chat management.

How to use MCP Telegram Server?

To use the MCP Telegram Server, clone the repository, install the required dependencies, configure your Telegram API credentials in a .env file, and run the server using the MCP command.

Key features of MCP Telegram Server?

  • Message search with basic, advanced, and regex pattern modes.
  • Chat management capabilities including listing dialogs and sending messages.
  • Analytics and data export functionality for chat statistics.
  • Robust error handling and logging.
  • Built on the Model Control Protocol (MCP) architecture.

Use cases of MCP Telegram Server?

  1. Searching for messages in Telegram chats.
  2. Managing and sending messages in various Telegram dialogs.
  3. Analyzing chat statistics and exporting data for reporting.

FAQ from MCP Telegram Server?

  • What are the prerequisites for using MCP Telegram Server?

You need Python 3.x and Telegram API credentials (API ID and API Hash).

  • Is there a community for support?

Yes! Join our Telegram Discussion Group for support and updates.

  • How do I install the MCP Telegram Server?

Clone the repository, install dependencies, configure your credentials, and run the setup script.

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

Recommend Servers

View All
Crevio

2 days ago
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