Telegram MCP Server

Created By
NexusX-MCPa year ago
An MCP server implementation that provides tools for interacting with the [Telegram Bot API](
Overview

what is Telegram MCP Server?

Telegram MCP Server is an implementation that provides tools for interacting with the Telegram Bot API, allowing AI assistants to send messages and retrieve bot information programmatically.

how to use Telegram MCP Server?

To use the Telegram MCP Server, set up the environment by installing the necessary packages, configure your bot token, and interact with the provided tools through the API.

key features of Telegram MCP Server?

  • Retrieve bot information with get_bot_info.
  • Send messages to chats using send_message.
  • Receive updates with get_updates using long polling.
  • Forward messages with forward_message.

use cases of Telegram MCP Server?

  1. Automating responses in Telegram chats.
  2. Building AI-driven chatbots that interact with users.
  3. Managing group chats and channels programmatically.

FAQ from Telegram MCP Server?

  • How do I get my bot token?

You can obtain your bot token by talking to @BotFather on Telegram and creating a new bot.

  • Is there a limit on the number of messages I can send?

Yes, Telegram has rate limits for sending messages to prevent spam.

  • Can I use this server for any type of bot?

Yes, as long as it adheres to Telegram's Bot API guidelines.

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