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
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

8 hours ago