Telegram Client Library and MCP Server

Created By
MCP-Mirrora year ago
Mirror of
Overview

what is the Telegram Client Library and MCP Server?

This project provides a Telegram client library and an MCP (Model Context Protocol) server that allows AI assistants to interact with Telegram.

how to use the Telegram Client Library and MCP Server?

To use the Telegram Client Library, set up your API credentials in a .env file, install dependencies, and run the example client. For the MCP server, start it and access it via the provided URL.

key features of the Telegram Client Library and MCP Server?

  • Telegram Client Library: Authentication with Telegram, session management, retrieving chats, and filtering messages.
  • MCP Server: Search channels by keywords, list available channels, retrieve messages, and filter messages by pattern.

use cases of the Telegram Client Library and MCP Server?

  1. Building AI assistants that can interact with Telegram channels.
  2. Automating message retrieval and filtering for data analysis.
  3. Creating custom Telegram bots that utilize the MCP server for enhanced functionality.

FAQ from the Telegram Client Library and MCP Server?

  • Can I use this project for any Telegram bot?

Yes! This library can be integrated into any Telegram bot that requires interaction with Telegram's API.

  • Is there support for two-factor authentication?

Yes! The library supports authentication with two-factor authentication.

  • How do I filter messages?

You can filter messages using regex patterns through the provided methods.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MCP-Mirror
Star
0
Language
JavaScript
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)

2 days ago