Telegram MCP Server ✨📲

Created By
elyasea year ago
Overview

what is Telegram MCP Server?

Telegram MCP Server is a simple server designed for interacting with Telegram, allowing users to perform various actions through a command-line interface.

how to use Telegram MCP Server?

To use the Telegram MCP Server, install the required package and connect to your Telegram account using a phone number and code. After setup, you can use various commands to interact with Telegram.

key features of Telegram MCP Server?

  • Easy setup with a single command for various clients.
  • Secure login with phone number and 2FA support.
  • Core Telegram actions like sending messages, listing chats, and retrieving chat history.

use cases of Telegram MCP Server?

  1. Automating message sending in Telegram.
  2. Managing and retrieving chat history for analysis.
  3. Integrating Telegram functionalities into other applications.

FAQ from Telegram MCP Server?

  • Is the Telegram MCP Server easy to set up?

Yes! It requires just a single command to install and configure.

  • Does it support two-factor authentication?

Yes! The server supports secure login with 2FA.

  • What programming language is it built with?

The Telegram MCP Server is built using Python.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
elyase
Star
0
Language
Python
License
-

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
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.

28 minutes ago