emailmd
Render markdown into email-safe HTML, lint drafts for deliverability problems, and preview emails.
Current official Telegram and TON docs: Bot API, Mini Apps, MTProto, TDLib, TON Connect, Tolk
Lists are ordered by a usage score (out of 100) built from these parts
| Popularity | 0/80 | GitHub stars or weekly downloads: the larger counts 60, the smaller 20 |
|---|---|---|
| Freshness | 12/12 | Full marks for a release or code change within 30 days |
| Still answering | 0/8 | The cloud endpoint answered at the last check |
| Usage score | 12/100 |
Quality: Passed 3/3 basic checks (shown, not used for ordering) · Momentum: No data yet (Used only on the Trending tab)
Pick the AI app you use, then copy the settings.
Let your AI install it with one sentence
Please install Telegram Dev. Follow https://mcp.popnx.com/i/kay0k1-telegram-dev.md, show me the commands and wait for my OK before running them.Paste it into an AI that can work on your computer (such as Claude Code or Cursor). It reads our steps, shows you the commands and waits for your OK. No key, no sign-up. · See the full text your AI reads
Passed 3/3 checks · Runs on your computer · ✓ Commands checked Nov 14, 2026
First: which AI do you use?
Pick your app and the steps appear below.
Works with Claude, with some setup first
Install Python (uv) on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone
Copy this message into a Claude chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Telegram Dev for Claude on this computer, in this order: 1) Check uv with uv --version. If it is missing, tell me to install it from https://docs.astral.sh/uv/getting-started/installation/; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "telegram-dev": { "command": "uvx", "args": [ "telegram-dev", "serve" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the Telegram Dev tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
uv --versionMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: uv has no click-through installer. Copy the one-line command for your system (macOS or Windows) from uv’s official page into Terminal · no separate Python install needed; uv downloads it when required
When it’s done, close Terminal, open it again and run the same command. You should see a version number: uv --version
Install once; it works for everything that needs uv
SettingsDeveloperEdit Config
{
"mcpServers": {
"telegram-dev": {
"command": "uvx",
"args": [
"telegram-dev",
"serve"
]
}
}
}Use Telegram Dev and tell me what you can do for me, then show me one thing✓ If Claude says it is using Telegram Dev or shows a Telegram Dev tool in the answer, you are connected
The command above works without these. Add them only if you want to change something, following the maker’s description.
TELEGRAM_KNOWLEDGE_DB Path to the SQLite documentation cache (default: the user cache directory)TELEGRAM_DOC_AUTO_SYNC Set to 0 to disable the background refresh cycleDescriptions are as written by the maker.
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
ChatGPT cannot connect Telegram Dev yet
Telegram Dev runs on your computer, but ChatGPT can only connect servers that run on the web
A · Use an app that can connect Telegram Dev
B · Others in Chat & email that work with ChatGPT
Picked from the most used in the same category, only ones that connect by address with no key
Works with Claude Code, with some setup first
Install Python (uv) on your computer first (one time)
Copy this message into a Claude Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Telegram Dev for Claude Code on this computer, in this order: 1) Check uv with uv --version. If it is missing, tell me to install it from https://docs.astral.sh/uv/getting-started/installation/; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): claude mcp add --scope user telegram-dev -- uvx telegram-dev serve 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the Telegram Dev tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
uv --versionMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: uv has no click-through installer. Copy the one-line command for your system (macOS or Windows) from uv’s official page into Terminal · no separate Python install needed; uv downloads it when required
When it’s done, close Terminal, open it again and run the same command. You should see a version number: uv --version
Install once; it works for everything that needs uv
Mac: press Command+Space and type Terminal · Windows: open PowerShell
claude mcp add --scope user telegram-dev -- uvx telegram-dev serveYou should see Telegram Dev listed as connected
Use Telegram Dev and tell me what you can do for me, then show me one thing✓ If Claude Code says it is using Telegram Dev or shows a Telegram Dev tool in the answer, you are connected
The command above works without these. Add them only if you want to change something, following the maker’s description.
TELEGRAM_KNOWLEDGE_DB Path to the SQLite documentation cache (default: the user cache directory)TELEGRAM_DOC_AUTO_SYNC Set to 0 to disable the background refresh cycleDescriptions are as written by the maker.
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with Cursor, with some setup first
Install Python (uv) on your computer first (one time)
Copy this message into a Cursor chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Telegram Dev for Cursor on this computer, in this order: 1) Check uv with uv --version. If it is missing, tell me to install it from https://docs.astral.sh/uv/getting-started/installation/; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "telegram-dev": { "command": "uvx", "args": [ "telegram-dev", "serve" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the Telegram Dev tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
uv --versionMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: uv has no click-through installer. Copy the one-line command for your system (macOS or Windows) from uv’s official page into Terminal · no separate Python install needed; uv downloads it when required
When it’s done, close Terminal, open it again and run the same command. You should see a version number: uv --version
Install once; it works for everything that needs uv
Use Telegram Dev and tell me what you can do for me, then show me one thing✓ If Cursor says it is using Telegram Dev or shows a Telegram Dev tool in the answer, you are connected
The command above works without these. Add them only if you want to change something, following the maker’s description.
TELEGRAM_KNOWLEDGE_DB Path to the SQLite documentation cache (default: the user cache directory)TELEGRAM_DOC_AUTO_SYNC Set to 0 to disable the background refresh cycleDescriptions are as written by the maker.
Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with VS Code, with some setup first
Install Python (uv) on your computer first (one time)
Copy this message into a VS Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Telegram Dev for VS Code on this computer, in this order: 1) Check uv with uv --version. If it is missing, tell me to install it from https://docs.astral.sh/uv/getting-started/installation/; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "servers": { "telegram-dev": { "type": "stdio", "command": "uvx", "args": [ "telegram-dev", "serve" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the Telegram Dev tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
uv --versionMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: uv has no click-through installer. Copy the one-line command for your system (macOS or Windows) from uv’s official page into Terminal · no separate Python install needed; uv downloads it when required
When it’s done, close Terminal, open it again and run the same command. You should see a version number: uv --version
Install once; it works for everything that needs uv
Use Telegram Dev and tell me what you can do for me, then show me one thing✓ If VS Code says it is using Telegram Dev or shows a Telegram Dev tool in the answer, you are connected
The command above works without these. Add them only if you want to change something, following the maker’s description.
TELEGRAM_KNOWLEDGE_DB Path to the SQLite documentation cache (default: the user cache directory)TELEGRAM_DOC_AUTO_SYNC Set to 0 to disable the background refresh cycleDescriptions are as written by the maker.
Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Claude Code
claude mcp add --scope user telegram-dev -- uvx telegram-dev serveClaude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"telegram-dev": {
"command": "uvx",
"args": [
"telegram-dev",
"serve"
]
}
}
}Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"telegram-dev": {
"command": "uvx",
"args": [
"telegram-dev",
"serve"
]
}
}
}VS Code (mcp.json)
{
"servers": {
"telegram-dev": {
"type": "stdio",
"command": "uvx",
"args": [
"telegram-dev",
"serve"
]
}
}
}TELEGRAM_KNOWLEDGE_DB envTELEGRAM_DOC_AUTO_SYNC envDescriptions are as written by the maker.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
pypi: telegram-devBased on how this server connects and on each app’s own docs, checked Nov 10, 2026.
Run on your computer in
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 20, 2026
The registry name was verified with the GitHub account Kay0k1, which owns the repo
Code last changed 2 days ago
Uses MIT
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
No entries on OSV.dev for telegram-dev@0.9.0
Checks only this package version, not every dependency · checked Nov 16, 2026
If you made this, paste this code into your README. The badge links back to this page.
[](https://mcp.popnx.com/en/servers/kay0k1-telegram-dev)Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.
No reviews yet
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed 2 days ago, and the latest version (0.9.0) reached the registry 9 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.
In the same category: emailmd, Kite Discord Bot Builder, e2a — email for AI agents, Infobip MCP, kernelCAD
Same category, other makers, commands already checked. Official ones first, then by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Render markdown into email-safe HTML, lint drafts for deliverability problems, and preview emails.
Build and fix Discord bots from a chat. Kite hosts them 24/7, with no code to deploy.
Authenticated email gateway for AI agents — per-agent inboxes, HITL approval, SPF/DKIM verified.
Infobip MCP server for omnichannel communication and messaging. SMS, RCS, WhatsApp, Viber and more.
CAD in ChatGPT and Claude: editable parts, STEP/STL/drawings, in-chat 3D, automatic checks.
| This one Telegram Dev | emailmd | Kite Discord Bot Builder | e2a — email for AI agents | Infobip MCP | kernelCAD | |
|---|---|---|---|---|---|---|
| Runs where | Installs on your computer | Cloud or install on your computer | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install |
| Needs a key | No | No | No | No | No | No |
| Add with + in Claude | No | No | No | No | Yes | No |
| Basic checks | 3/3 | 5/5 | 4/4 | 4/4 | 4/4 | 4/4 |
| License | MIT | MIT | AGPL-3.0 | Apache-2.0 | MIT | MIT |
| Price | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry |
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Keep Telegram bots and AI coding agents on the current Bot API.
Telegram changes the Bot API every month or two, and both code and models fall behind. Telegram Dev has three parts:
No Telegram account, bot token or API key is needed: everything reads public documentation.
telegram-dev check checks every Bot API call in a Python bot — aiogram, python-telegram-bot, pyTelegramBotAPI or raw HTTP requests to api.telegram.org — in one run, and prints only the findings:
uvx telegram-dev check ./my-bot
$ uvx telegram-dev check ./tutorial # a popular open-source aiogram 3 tutorial
code/03_buttons/bot.py:79: warning: types.KeyboardButton: request_user was retired in Bot API 7.0: Renamed the field request_user in the class KeyboardButton to request_users. The old name will still work for backward compatibility. ... code/08_inline_mode/handlers/inline_mode.py:48: warning: inline_query.answer: switch_pm_text was retired in Bot API 6.7: ... replacing the parameters switch_pm_text and switch_pm_parameter of the method answerInlineQuery with the parameter button of type InlineQueryResultsButton. ... Bot API 10.4; 95 files with bot code; libraries: aiogram ==3.14.0 ==3.7.0 >=3.24.0 ...; 0 errors, 5 warnings
A wrong value is an error, for example InlineKeyboardButton(text="Delete", style="red") gives style: must be one of danger, success, primary.
Errors are values outside the documented list and unknown methods or parameters in raw API requests. Warnings are parameters Telegram retired (with the version and the changelog entry that replaced them), keyword arguments that are neither Bot API parameters nor known library options, and bot methods with no Bot API counterpart. It reads code without running it, so it does not follow variables or check required parameters. Options: --json, --exclude 'tests/*', --strict (fail on warnings), --format github. In an agent session the same check is the check_telegram_project tool (local stdio server only, since it reads files).
On a GitHub repository, run it on every pull request; findings appear as annotations on the changed lines:
# .github/workflows/telegram.yml
on: [pull_request] jobs: bot-api: runs-on: ubuntu-latest steps:
You need uv. No bot token, Telegram account or API key is needed: the server only reads public documentation.
Run this in your project directory:
uvx telegram-dev install --agent claude # or: codex, cursor
--agent | MCP server is added to | Skill is copied to |
|---|---|---|
claude | .mcp.json | .claude/skills/telegram-dev |
codex | .codex/config.toml | .agents/skills/telegram-dev |
cursor | .cursor/mcp.json | .cursor/skills/telegram-dev |
The installer keeps your other settings, backs up the files it changes and never overwrites an existing Telegram Dev setup. The server is pinned to the installed version, so nothing has to stay on disk besides the uv cache. Open a new agent session afterwards and approve the project MCP server when asked. Codex loads project settings only after you trust the project directory.
To upgrade later: uvx telegram-dev@latest install --agent claude --update.
/plugin marketplace add Kay0k1/telegram-dev
/plugin install telegram-dev@telegram-dev-tools
This adds the skill and the MCP server for all your projects. Use either the plugin or the installer, not both.
claude mcp add --scope user telegram-knowledge -- uvx telegram-dev serve
codex mcp add telegram-knowledge -- uvx telegram-dev serve
Cursor:
Any other MCP client:
{
"mcpServers": { "telegram-knowledge": { "command": "uvx", "args": ["telegram-dev", "serve"] } } }
The tools work without the skill, but the skill is what makes an agent use them consistently.
Telegram ships a new Bot API version every month or two. A model's knowledge of it stops at its training cutoff, so agents confidently write code against fields that changed or never existed. They also mix up the Bot API, MTProto and TDLib, which have very different capabilities.
TON moves just as fast. The current TON docs call the coin Gram, describe Telegram Money, the wallet built into Telegram, and treat Tolk as the main contract language with FunC as legacy. On top of that, Telegram has its own rules: blockchain features in Mini Apps must use TON and TON Connect, and digital goods are sold for Stars.
With Telegram Dev the agent reads the current page before it writes code. A real Codex CLI run in a fresh project after uvx telegram-dev install --agent codex (tool calls trimmed):
> Use the telegram-dev skill. In a python-telegram-bot project, I want the inline
'Delete' button to be red and show a custom emoji. Which Bot API fields do this, what are the requirements, and what does the request JSON look like?
get_telegram_corpus_status {} search_telegram_docs {"query": "style icon_custom_emoji_id", "area": "releases"} search_telegram_docs {"query": "InlineKeyboardButton icon_custom_emoji_id style", "area": "bot-api"} get_telegram_document {"url": "https://core.telegram.org/bots/api", "offset": 167594, "length": 10500} get_telegram_document {"url": "https://core.telegram.org/bots/api-changelog", "offset": 39089, "length": 6000}
Use these InlineKeyboardButton fields:
The custom emoji requires either a bot that bought additional usernames on Fragment, or a Premium bot owner with the message sent by the bot to a private chat, group or supergroup. PTB 22.7+ supports both fields. Older Telegram clients show the button unstyled. Source: https://core.telegram.org/bots/api#inlinekeyboardbutton
{"chat_id": 123456789, "text": "Choose an action:", "reply_markup": {"inline_keyboard": [[{"text": "Delete", "callback_data": "delete:42", "style": "danger", "icon_custom_emoji_id": "YOUR_CUSTOM_EMOJI_ID"}]]}}
The skill also knows when *not* to reach for a blockchain. Another real Codex run:
> Use the telegram-dev skill. Our Telegram Mini App sells a premium in-game skin
for 2 TON. I want a Buy button that connects the user's wallet and charges them.
get_telegram_document {"url": "https://core.telegram.org/bots/payments-stars", "refresh": true} search_telegram_docs {"query": "createInvoiceLink answerPreCheckoutQuery successful_payment XTR", "area": "bot-api"} get_telegram_document {"url": "https://docs.ton.org/applications/ton-connect/overview", "refresh": true} get_telegram_document {"url": "https://core.telegram.org/bots/webapps", "offset": 40310}
Use Telegram Stars (XTR) through the Bot API. The skin is a digital good, so Telegram requires Stars and prohibits cryptocurrency payment for this purchase. For permitted wallet features, use the TON Connect SDK.
| Tool | What it does |
|---|---|
search_telegram_docs | Full-text search over indexed sections, optionally limited to one area: bot-api, mini-apps, telegram-api, tdlib, ton, releases, ton-releases, aiogram, python-telegram-bot, grammy and others. Core Telegram docs rank first unless the query names a library |
get_telegram_document | Reads an official page in pages of up to 40,000 characters; fetches it if it is missing or older than 6 hours |
get_telegram_corpus_status | What is indexed, how fresh it is and which sources failed |
list_telegram_document_revisions | Revisions of a page captured by this installation |
list_telegram_sources | The 61 official entry points, grouped by API area |
list_telegram_cached_pages | Pages already stored in the local cache, by area, with freshness |
get_bot_api_definition | One Bot API method or type as structured data: parameters or fields, types, required flags, allowed values, length limits, and the changelog entries that mention it |
check_bot_api_call | Checks a request your code sends against the current Bot API schema: unknown methods and parameters (with suggestions), missing required ones, wrong types, values outside the documented list, retired parameters with the version that replaced them |
list_bot_api_changes | Official Bot API changelog as structured releases, filtered by version (since_version="9.0") or by a method, type or field name |
check_telegram_project | Checks every Bot API call in a local Python bot project in one run (see Check a bot project); local stdio server only |
The Bot API tools are built from the official API page and changelog in the cache, so they follow Telegram's current version (Bot API 10.4 at the time of writing) without a hand-written schema. For example, check_bot_api_call on
{"method": "sendMessage", "params": {"chat_id": 1, "text": "Delete?", "reply_to_message_id": 42,
"reply_markup": {"inline_keyboard": [[{"text": "Delete", "callback_data": "del", "style": "red"}]]}}}
returns an error for reply_markup.inline_keyboard0.style (must be one of danger, success, primary) and a warning that reply_to_message_id was replaced by reply_parameters in Bot API 7.0. It does not call Telegram, so permissions, chat state and file contents still need a real test.
The cache starts empty. Pages are fetched the first time the agent reads them and indexed right away. To pre-fetch everything reachable from the configured sources:
uvx telegram-dev sync --max-pages 0
uvx telegram-dev search "sendVideoNote" uvx telegram-dev status
| Area | What the agent checks |
|---|---|
| Bot API | Messages, keyboards, updates, webhooks, files, permissions |
| Formatting and emoji | Entities, UTF-16 offsets, custom emoji and who may use them |
| Media and stickers | Voice messages, video notes, sticker sets, fi