Telegram MCP Server

Created By
kfastova year ago
MCP server implementation for Telegram
Overview

what is Telegram MCP Server?

Telegram MCP Server is a project that provides a Telegram client library and an MCP (Model Context Protocol) server, enabling AI assistants to interact with Telegram.

how to use Telegram MCP Server?

To use the Telegram MCP Server, set up your environment with your Telegram API credentials, install the necessary dependencies, and run the server to interact with Telegram channels and messages.

key features of Telegram MCP Server?

  • Authentication with Telegram (including 2FA support)
  • Session management for automatic reuse of existing sessions
  • Retrieving chats and messages from specific channels
  • Filtering messages using regex patterns
  • Searching for channels by keywords

use cases of Telegram MCP Server?

  1. Building AI assistants that can interact with Telegram channels.
  2. Automating message retrieval and filtering for data analysis.
  3. Creating chatbots that can manage and respond to messages in Telegram.

FAQ from Telegram MCP Server?

  • Can I use this server with any AI assistant?

Yes! The MCP server can be used with any MCP-compatible assistant.

  • Is there a limit to the number of channels I can access?

No, you can access all channels that your Telegram account has access to.

  • How do I filter messages?

You can filter messages by applying regex patterns to the retrieved messages.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
kfastov
Star
12
Language
JavaScript
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