Telegram MCP Bridge
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| VERCEL_URL | Yes | Your Vercel deployment URL (e.g., https://my-telegram-bot.vercel.app). This is used by the local proxy to communicate with the Telegram backend. |
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
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| ask_telegram_confirmationC | Sends a question to the user via Telegram and waits for a YES/NO response. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The tool's purpose—sending a yes/no confirmation question via Telegram—is clearly distinct by default.
A single tool inherently has perfect naming consistency, as there are no other tools to compare it against. The name 'ask_telegram_confirmation' follows a clear verb_noun pattern.
One tool is too few for a server named 'Telegram MCP Bridge,' which implies broader Telegram functionality. This feels thin and incomplete for the apparent scope of bridging Telegram interactions.
The tool set is severely incomplete for a Telegram bridge. It lacks basic operations like sending messages, receiving updates, managing chats, or handling files, leaving major gaps in the domain coverage.