Telegram Relay Rich Markdown MCP
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Telegram Relay Rich Markdown MCPsend a rich markdown release announcement to the channel"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Telegram Relay Rich Markdown MCP
A small, private Model Context Protocol server that lets ChatGPT or another MCP client send Telegram Rich Markdown to one fixed Telegram destination.
The server is intentionally narrow: it exposes one write tool, cannot choose another chat, and does not provide Telegram administration capabilities.
Features
Sends Telegram Rich Markdown through
sendRichMessage.Supports headings, lists, task lists, tables, links, quotations, details, spoilers, footnotes, code, and LaTeX formulas.
Uses one destination configured by
TELEGRAM_CHANNEL_ID.Protects the MCP endpoint with a high-entropy capability URL.
Blocks remote media embeds and unsafe URL schemes.
Suppresses accidental duplicate messages.
Applies a small best-effort per-instance rate limit.
Avoids logging message text, bot tokens, destination IDs, or token-bearing Telegram URLs.
Deploys on Vercel.
Security model
The MCP endpoint is:
https://YOUR-DOMAIN/<MCP_ACCESS_TOKEN>/mcpTreat the complete URL as a password. This capability-URL approach is suitable for a private, single-user deployment. For a public or multi-user integration, replace it with a standards-based OAuth 2.1 authorization flow.
The tool cannot receive a chat_id; the destination only comes from the server environment. It also does not implement message editing, deletion, member management, webhooks, invite links, paid broadcasts, or other Telegram administration methods.
Remote media blocks are rejected intentionally. Normal text formatting, links, tables, details, quotations, spoilers, footnotes, code, and formulas remain available.
Required environment variables
Variable | Required | Description |
| Yes | Bot token issued by |
| Yes | Fixed Telegram destination ID or public channel username. |
| Yes | URL-safe random secret with at least 32 characters. |
| No | Defaults to |
| No | Defaults to |
| No | Defaults to |
| No | Defaults to |
Generate the MCP access token with:
openssl rand -hex 32Telegram destination IDs
Use the ID exactly as returned by Telegram:
Destination | Example |
Private user chat |
|
Basic group |
|
Supergroup or channel |
|
Public channel |
|
For a private bot conversation, first open the bot and send /start. Then retrieve the chat ID:
$updates = Invoke-RestMethod "https://api.telegram.org/bot$token/getUpdates"
$updates.result | ForEach-Object {
if ($_.message) {
$_.message.chat
}
}Use the returned message.chat.id without modifying it.
Local development
npm install
cp .env.example .env.local
npm run devThe local endpoint is:
http://localhost:3000/<MCP_ACCESS_TOKEN>/mcpA non-secret health endpoint is available at:
http://localhost:3000/healthIt reports only whether each required setting is present, never its value.
Deploy to Vercel
Import this repository into Vercel.
Add the required environment variables for Production and Preview.
Deploy.
Connect your MCP client using:
https://YOUR-PROJECT.vercel.app/<MCP_ACCESS_TOKEN>/mcpOnce the GitHub repository is connected, pushes to main create production deployments and pull requests create preview deployments.
Example Rich Markdown
# Release update
**Version 2.4 is live.**
- Faster imports
- Better error messages
- New analytics table
| Metric | Result |
| --- | ---: |
| Build time | 42 s |
| Tests | 318 passed |
> Deployment completed successfully.
<details>
<summary>Technical notes</summary>
The complexity is $O(n \log n)$.
</details>Limitations
The in-memory rate limit and duplicate cache are best-effort because Vercel instances do not share memory.
Remote images and other remote media embeds are blocked.
Telegram bots cannot initiate a private conversation until the user has contacted the bot.
Rich Markdown support depends on the Telegram Bot API version available to the bot.
License
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/sandoche/telegram-relay-richmarkdown-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server