Skip to main content
Glama
tensakulabs

telegram-mcp

by tensakulabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
TELEGRAM_PHONENoPhone number for authentication
TELEGRAM_API_IDYesYour Telegram API ID
TELEGRAM_API_HASHYesYour Telegram API hash
TELEGRAM_ENV_PATHNoPath to .env file
TELEGRAM_SESSION_DIRNoDirectory for session file

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
send_messageA

Send a message to a Telegram bot and wait for its reply.

Args:
    bot: Bot username (e.g. '@BotFather' or 'BotFather')
    message: The message text to send
    timeout: Seconds to wait for a reply (default 30)
get_historyA

Get message history with a Telegram bot.

Args:
    bot: Bot username (e.g. '@BotFather' or 'BotFather')
    limit: Number of messages to retrieve (default 20)

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A3.9/5.0

Scored across 2 tools

Disambiguation5/5

The two tools have clearly distinct purposes: one retrieves message history, the other sends a message and waits for a reply. No overlap or ambiguity.

Naming Consistency5/5

Both tools follow a consistent verb_noun pattern in snake_case (get_history, send_message), making them predictable and easy to understand.

Tool Count2/5

With only 2 tools for a Telegram bot server, the surface is too thin. Typical Telegram interactions require more operations (e.g., listing bots, deleting messages), making this feel incomplete.

Completeness2/5

Obvious gaps exist: no tool to list available bots, delete messages, get updates, or handle multiple bots. The set covers only basic send and retrieve operations.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources