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.
제작자가 쓴 원문
목록은 사용 점수(100점 만점)로 정렬되며 구성은 다음과 같습니다
| 인기 | 0/80 | GitHub 별 또는 주간 다운로드: 큰 쪽 60, 작은 쪽 20 |
|---|---|---|
| 최신성 | 12/12 | 30일 안에 릴리스나 코드 변경이 있으면 만점 |
| 응답 중 | 0/8 | 마지막 점검 때 클라우드 엔드포인트가 응답 |
| 사용 점수 | 12/100 |
품질: 기본 점검 3/3개 통과(표시만, 정렬에는 안 씀) · 상승세: 데이터 없음 (급상승 탭에서만 사용)
쓰고 있는 AI 앱을 고른 다음 설정을 복사하세요.
검사 3/3 통과 · 내 컴퓨터에서 실행돼요
먼저: 어떤 AI를 쓰시나요?
쓰는 앱을 고르면 아래에 단계가 나옵니다.
Claude에 연결할 수 있지만 먼저 준비가 필요해요
키 필요 없음, 설치 필요 없음 · 컴퓨터용 Claude 앱(Windows 또는 Mac)에서만 되고 웹이나 모바일은 안 돼요
Telegram (kotlogramme)을 써서 나에게 무엇을 해 줄 수 있는지 알려 주고, 하나 해 봐✓ Claude가 Telegram (kotlogramme)을 쓰고 있다고 하거나 답에 Telegram (kotlogramme) 도구 이름이 나오면 연결된 거예요
메뉴 이름은 2026년 11월 11일에 Anthropic 도움말에서 확인 · 앱 버전에 따라 화면이 조금 다를 수 있어요
ChatGPT는 아직 Telegram (kotlogramme)에 연결할 수 없어요
Telegram (kotlogramme)는 내 컴퓨터에 설치해서 쓰지만 ChatGPT는 웹에서 도는 서버만 연결할 수 있어요
A · Telegram (kotlogramme)에 연결되는 앱 쓰기
B · 채팅 및 이메일에서 ChatGPT에 연결되는 다른 서버
같은 분류에서 많이 쓰는 것 중 키 없이 주소만으로 연결되는 것을 골랐어요
Claude Code는 아직 Telegram (kotlogramme)에 연결할 수 없어요
제작자가 컴퓨터용 Claude 앱 설치 파일만 제공해요
A · Telegram (kotlogramme)에 연결되는 앱 쓰기
Cursor는 아직 Telegram (kotlogramme)에 연결할 수 없어요
제작자가 컴퓨터용 Claude 앱 설치 파일만 제공해요
A · Telegram (kotlogramme)에 연결되는 앱 쓰기
VS Code는 아직 Telegram (kotlogramme)에 연결할 수 없어요
제작자가 컴퓨터용 Claude 앱 설치 파일만 제공해요
A · Telegram (kotlogramme)에 연결되는 앱 쓰기
mcpb: …/kotlogramme-0.11.1-linux-aarch64.mcpbmcpb: …/kotlogramme-0.11.1-linux-x86_64.mcpbmcpb: …/kotlogramme-0.11.1-macos-aarch64.mcpb이 서버의 연결 방식과 각 앱의 공식 문서를 바탕으로 했어요. 2026년 11월 10일 확인.
내 컴퓨터에서 실행하는 앱
ClaudeGooseLM StudioMsty StudioCherry StudioVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
내 컴퓨터에서 실행돼요. 설치하면 AI 앱에 도구 목록이 나타나요.
누구나 볼 수 있는 정보를 점검했고, 코드는 읽지 않았어요. 해당하지 않는 항목은 개수에서 뺐어요. · 2026년 11월 20일 점검
레지스트리 이름이 GitHub 계정 J0s3f 기준으로 확인되었고, 이 계정이 저장소를 소유하고 있어요
코드 마지막 변경: 10일 전
Apache-2.0 사용
내 컴퓨터에서 실행되는 서버라 인터넷 엔드포인트가 없어요
내 컴퓨터에서 실행되며, 대신 로컬 설정을 사용해요
내 컴퓨터에서 실행돼요. 도구 목록은 인터넷 엔드포인트가 있는 서버에서만 읽을 수 있어요
제작자라면 이 코드를 README에 붙여 넣으세요. 배지는 이 페이지로 연결됩니다.
[](https://mcp.popnx.com/en/servers/j0s3f-kotlogramme)질문하고, 팁을 나누고, 안 되는 점을 알려 주세요. "도움이 됨"이 많은 순서예요.
아직 리뷰가 없어요
레지스트리에서 이 카테고리의 활성 서버 전체와 비교했어요. 스타는 게시자가 저장소를 소유한 경우에만 세요.
해당하는 기본 점검 3개 중 3개를 통과했어요. 코드는 읽지 않았어요. 키나 토큰을 넣기 전에 서버가 어떤 권한을 요구하는지 확인하고, 꼭 필요한 권한만 있는 키를 쓰세요.
레지스트리에 필수 키가 나와 있지 않아요. 다만 처음 쓸 때 로그인을 요구하는 서버도 있어요.
내 컴퓨터에서 실행돼요. AI 앱이 필요할 때 실행하고, 데이터는 제작자의 서버를 거치지 않아요(서버 자체가 온라인 서비스를 호출하는 경우는 제외).
GitHub 저장소는 마지막으로 10일 전 변경됐고, 최신 버전(0.11.1)은 12일 전 레지스트리에 올라왔어요.
Claude Desktop, Claude Code, Cursor, VS Code처럼 MCP를 지원하는 앱에서 쓸 수 있어요. 내 컴퓨터에 MCPB도 있어야 해요.
같은 카테고리에는: emailmd, Kite Discord Bot Builder, e2a — email for AI agents, Infobip MCP, kernelCAD
같은 카테고리, 다른 제작자, 명령 확인 완료. 공식이 먼저, 그다음 스타 순.
카드 보는 법:↓ 주간 다운로드i★ GitHub 스타i세 기둥: 리뷰 · 점검 · 사용 정도i업데이트 = 최신 버전을 레지스트리에 공개한 날i
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.
| 이 항목 Telegram (kotlogramme) | emailmd | Kite Discord Bot Builder | e2a — email for AI agents | Infobip MCP | kernelCAD | |
|---|---|---|---|---|---|---|
| 실행 위치 | 컴퓨터에 설치 필요 | 클라우드 또는 컴퓨터 설치 모두 가능 | 클라우드에서 동작, 설치 불필요 | 클라우드에서 동작, 설치 불필요 | 클라우드에서 동작, 설치 불필요 | 클라우드에서 동작, 설치 불필요 |
| 키 필요 | 아니요 | 아니요 | 아니요 | 아니요 | 아니요 | 아니요 |
| Claude에서 +로 추가 | 아니요 | 아니요 | 아니요 | 아니요 | 예 | 아니요 |
| 기본 점검 | 3/3 | 5/5 | 4/4 | 4/4 | 4/4 | 4/4 |
| 라이선스 | Apache-2.0 | MIT | AGPL-3.0 | Apache-2.0 | MIT | MIT |
| 가격 | 등록 정보에 비용 없음 | 등록 정보에 비용 없음 | 등록 정보에 비용 없음 | 등록 정보에 비용 없음 | 등록 정보에 비용 없음 | 등록 정보에 비용 없음 |
제작자의 저장소에서 쓰인 그대로 가져왔어요. PopNx MCP가 검토하거나 보증한 내용이 아니에요. HTML, 이미지, 스크립트는 제거했어요. 링크를 누르면 이 사이트를 벗어나요.
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