emailmd
Render markdown into email-safe HTML, lint drafts for deliverability problems, and preview emails.
Read and, if allowed, act on your own Telegram account: chats, messages, contacts, files.
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.
Passed 3/3 checks · Runs on your computer
First: which AI do you use?
Pick your app and the steps appear below.
Works with Claude, with some setup first
No key, nothing to install · Only the Claude desktop app (Windows or Mac), not the web or phone
Download the maker’s .mcpb file
The .mcpb file comes straight from the maker; we do not change it
Use Telegram (kotlogramme) and tell me what you can do for me, then show me one thing✓ If Claude says it is using Telegram (kotlogramme) or shows a Telegram (kotlogramme) tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
ChatGPT cannot connect Telegram (kotlogramme) yet
Telegram (kotlogramme) runs on your computer, but ChatGPT can only connect servers that run on the web
A · Use an app that can connect Telegram (kotlogramme)
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
Claude Code cannot connect Telegram (kotlogramme) yet
The maker only provides an installer for the Claude desktop app
A · Use an app that can connect Telegram (kotlogramme)
Cursor cannot connect Telegram (kotlogramme) yet
The maker only provides an installer for the Claude desktop app
A · Use an app that can connect Telegram (kotlogramme)
VS Code cannot connect Telegram (kotlogramme) yet
The maker only provides an installer for the Claude desktop app
A · Use an app that can connect Telegram (kotlogramme)
mcpb: …/kotlogramme-0.11.1-linux-aarch64.mcpbmcpb: …/kotlogramme-0.11.1-linux-x86_64.mcpbmcpb: …/kotlogramme-0.11.1-macos-aarch64.mcpbBased on how this server connects and on each app’s own docs, checked Nov 10, 2026.
Run on your computer in
ClaudeGooseLM StudioMsty StudioCherry StudioVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantCodex 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 J0s3f, which owns the repo
Code last changed 10 days ago
Uses Apache-2.0
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
Not checked: only npm and PyPI packages with a version can be checked
If you made this, paste this code into your README. The badge links back to this page.
[](https://mcp.popnx.com/en/servers/j0s3f-kotlogramme)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 10 days ago, and the latest version (0.11.1) reached the registry 12 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need MCPB 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 (kotlogramme) | 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 | Apache-2.0 | 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.
A command-line Telegram client written in Kotlin, built on the kotlogramme facade.
It aims to be two things at once: a genuinely useful, scriptable client for the terminal, and the reference consumer that exercises the whole kotlogramme surface so its gaps are found by a real application.
Status: usable. Phases 1-9 are implemented: authentication, configuration, dialogs, history,
sending and editing, media and files, contacts, search, chat members, dialog folders, live
updates, an interactive shell, admin rights, stickers and inline. The current release is
v0.11.1, carrying the fat jar and
the distribution; it builds on the
kotlogramv0.9.15tag from JitPack. Later additions beyond
the original phases:
download-media,list-fileswith a server-side media-kind filter, and an upload progress bar for
send-file. Received messages render their formatting, and a message's inline bot is
resolved to
@username; seedocs/features.mdfor what ships and
docs/plan.mdfor what is left (album sends, chunked download with a progress view,
blocking, and the bot-safe numeric peer lookup).
kotlogramme config set --api-id <id> --api-hash <hash> # from my.telegram.org
kotlogramme login --phone +491700000000 # prompts for the code, then 2FA if set kotlogramme dialogs --limit 20 kotlogramme history @some_chat --limit 50 kotlogramme send @some_chat "hello from the terminal" kotlogramme send-file @some_chat clip.mp4 # detects the kind: a streamable video kotlogramme send-file @some_chat clip.mp4 --no-detect # ...or send the raw bytes as a document cat photo.png | kotlogramme send-file @some_chat - --name photo.png # ...or pipe the bytes on stdin kotlogramme list-files @some_chat --kind video # the chat's videos, filtered by Telegram kotlogramme download-media @some_chat 12345 # save a message's media, named after it kotlogramme stickers # installed sticker sets kotlogramme listen # follow new messages kotlogramme shell # interactive REPL
listen [--once] [--all] [--json] [--chat ] follows the live update stream. Read receipts, contact status and other updates without a message are hidden unless --all is given, and then print their content as JSON. --chat shows only messages from that chat, so listen --once --chat @ada waits for the next message there. --once stops after the first shown update, --json prints one object per line, and Ctrl-C ends the command cleanly. The stream is followed on the library's own background update loop, which polls in short waits and joins its thread on stop, so a stop costs at most one of those short polls rather than the library's 30 s one.
list-files lists a chat's files, filtered by media kind on Telegram's side rather than by scanning history, so it reaches the whole chat and not just the part a history read has covered. --kind names the filter (photo, video, photo-video, document, audio, voice, gif, animation), --limit caps the page, and --total prints just how many files the chat holds.
download-media [ ] writes a message's media to a local file. Without a target the file is named after the media's own name, falling back to the message id, and lands in the working directory; missing parent directories are created and an existing file is overwritten. The command prints the path and the byte count, so a script can read either.
Every command renders as a table by default. The global --plain and --json options, which go before the command (kotlogramme --json history @ada), switch one run to tab-separated plain text or to JSON, and --table forces the table; config set --format stores the default. In JSON every output line is one JSON value: a table is an array of objects, a statement is {"message": "..."}, a count is {"count": N}, and a listing cut short ends with {"next_after": "..."}. import-contacts --from-json FILE (- for stdin) takes a JSON array of {"phone", "first_name", "last_name"} objects. Tables wrap to the width of the terminal; --table-width N before the command sets the width yourself (0 never wraps), which is also how to get a wrapped table into a file. kotlogramme doctor checks the installation: the native library, the Telegram schema, the terminal libraries, the configuration and the network, without needing API credentials, and the account too when they are set.
kotlogramme mcp runs the client as a Model Context Protocol server over stdin and stdout. Log in once with kotlogramme login, then register the command with your AI application, for example in Claude Desktop's claude_desktop_config.json:
{ "mcpServers": { "telegram": {
"command": "C:\\Tools\\console\\kotlogramme.exe", "args": ["mcp"], "env": { "TG_API_ID": "...", "TG_API_HASH": "..." } } } }
or claude mcp add telegram -- kotlogramme mcp for Claude Code. By default it is read only: it can list chats, read and search messages, list contacts, members and sessions, and wait for the next message. --access read-write adds sending, editing, forwarding, reacting and pinning; --access full adds deleting, removing and blocking people, changing admin rights and ending sessions. An AI application that can write acts as you and reaches real people, so choose the lowest level that does the job. --files-dir adds tools that send files from that directory and save downloads into it, and nothing outside it. Message texts come from other people, so the server tells the model to treat them as data, not as instructions. The tools are listed in docs/features.md.
AI agents: to download and install the server for a person, follow docs/agent-install.md.
send-file draws a one-line progress bar while the bytes go out, showing the percentage, the bytes sent so far, the total and the current rate:
kotlogramme send-file @some_chat clip.mp4
The bar is on by default when the output is a terminal, and off when it is piped or redirected, so a script gets no carriage returns in its output. --progress forces it on and --no-progress turns it off; --no-progress wins if both are given, exactly as --no-color wins over --color. Only send-file uploads bytes, so only send-file has these flags. With --no-color the bar is plain ASCII. An upload that finishes before the first tick draws nothing at all, and the line is erased whether the upload finished, failed or was interrupted with Ctrl-C.
Piped input is spooled to a temporary file before the upload starts, because Telegram has to be told the total before the first part is sent and a pipe carries no length. The spool file is what makes a cat photo.png | kotlogramme send-file @some_chat - upload the exact bytes that were piped, and it also gives the bar a real total, so a piped upload gets a percentage too. The spool file is deleted once the upload ends, whichever way it ended. The one cost is that the bytes pass through the system's temporary directory once: that costs disk I/O rather than memory, and the upload itself still streams in chunks rather than holding the whole file in the heap.
The current release is v0.11.1. Its GitHub Release carries the JVM artifacts below and five single-file native executables:
java -jar kotlogramme-all.jar --help
distZip distribution. Unpack it and run kotlogramme-0.11.1/bin/kotlogramme (or kotlogramme-0.11.1\bin\kotlogramme.bat on Windows); the jar and its dependencies live in lib/.kotlogramme-0.11.1-windows-x86_64.exe and kotlogramme-0.11.1-{linux,macos}-{x86_64,aarch64}. Run the downloaded file directly; on Linux/macOS first use chmod +x. These require no JRE, JDK or installer. Support libraries are embedded by Wrappe and extracted into a temporary cache. See native requirements.api_id and api_hash from https://my.telegram.org, set with kotlogramme config set or the TG_API_ID/TG_API_HASH environment variables.kotlogramme login), or a bot token. Reading dialogs, history and a chat's files needs an ordinary account.The client is built from these libraries. The distribution is self-contained - they are all bundled into kotlogramme-all.jar, so none has to be installed - and each keeps its own licence.
com.github.J0s3f:kotlogram - the facade this client exercises, pinned by tag (see Picking the facade version); it carries grammers and the six native Telegram libraries.--json output format and the configuration file../gradlew build # compile and run the offline test suite
./gradlew installDist # build the runnable distribution build/install/kotlogramme/bin/kotlogramme --help
On Windows, use gradlew.bat and the generated build\install\kotlogramme\bin\kotlogramme.bat.
Standalone GraalVM builds packed with Wrappe run without a JRE or JDK on Windows x86_64 and Linux/macOS x86_64 and ARM64:
.\scripts\build-native-windows.ps1
build\distributions\kotlogramme-0.1.0-SNAPSHOT-windows-x86_64.exe --help
The script uses C:\Tools\graalvm-jdk-25.0.4+7.1 by default. Building also needs the MSVC C++ tools and Windows SDK. It compiles the native client and uses Wrappe to create and test one portable executable. CI uses Liberica NIK 25 on all five native targets; releases contain their single-file executables alongside the bundled jar and Java zip. Windows ARM64 uses the JVM distribution. See docs/native-image.md for setup, platform requirements and verification.
The client depends on the facade's v0.9.15 tag, resolved from JitPack. To pin a different one, pass it explicitly - any published facade tag works:
./gradlew test -PkotlogrammeVersion=<tag>
docs/plan.md — the implementation plan of record.docs/architecture.md — how the code is organised, and why.docs/decisions.md — design decisions and their rationale.docs/features.md — user-facing features that actually ship.docs/native-image.md — building and verifying standalone native packages.AGENTS.md](AGENTS