Skip to main content
Glama
nullnumber1

Telegram Community MCP

by nullnumber1
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
CHAT_IDSYesComma-separated list of chat IDs to index
TELEGRAM_API_IDYesYour Telegram API ID from my.telegram.org
TELEGRAM_API_HASHYesYour Telegram API hash from my.telegram.org

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
searchA

Search Telegram community messages.

mode=fts — exact word search (fast).
mode=semantic — meaning-based search (finds similar).
mode=hybrid — both combined with rank fusion (recommended).
chat_id — filter by specific chat.
date_from/date_to — ISO date filter, e.g. "2024-01-01".
get_contextB

Get thread context around a message: window messages before/after, plus all replies to the message.

list_chatsA

Show indexed chats: name, ID, message count, last sync date.

syncA

Sync new messages from Telegram.

Without arguments — all configured chats.
With chat_id — only the specified chat.
Returns the number of added messages.
get_statsA

Index statistics: total messages, per-chat breakdown, DB size.

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.7/5.0

Scored across 5 tools

Disambiguation5/5

Each tool targets a distinct operation: sync ingests messages, get_stats reports index metrics, search queries messages, get_context expands a thread, and list_chats enumerates chats. Search and get_context both retrieve messages but are clearly differentiated (query vs. thread expansion around a known message). No meaningful overlap.

Naming Consistency4/5

Three tools follow a clean verb_noun pattern (get_stats, get_context, list_chats), while sync and search are bare verbs. This is a minor deviation but still readable and consistent in spirit (all lowercase snake_case).

Tool Count5/5

Five tools is well within the ideal 3-15 range and each earns its place in the ingest-search-context lifecycle. Nothing is redundant or superfluous.

Completeness4/5

The read/index domain is well covered: sync, stats, search, thread context, and chat listing form a coherent lifecycle. Minor gaps exist (no fetch-by-message-ID, no chat add/remove or re-index management), but agents can work around these via search and list_chats.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources