Skip to main content
Glama
liagha

termgram

by liagha
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

Related Servers

Alternatives to termgram

Related Servers

  • chatmux

    echoedinvoker
    A
    license
    Not graded
    quality
    B
    maintenance
    Local-first MCP server that puts your own LINE and Telegram chats behind one data layer — a daemon on your machine logs in with your own account, stores messages to JSONL + SQLite/FTS5, and exposes 6 MCP tools over streamable HTTP on 127.0.0.1. Not a hosted service and not an npx one-liner: you clone the repo, run the daemon, and log in yourself.
    21 npm
    1
    MIT

  • Telegram MCP

    francescomiliani
    A
    license
    Not graded
    quality
    C
    maintenance
    Personal read-only Telegram MCP server exposing chat, message, and media tools via streamable HTTP with bearer authentication.
    1
    Apache 2.0

  • Telegram Agent for Codex

    Frejixxx
    A
    license
    Not graded
    quality
    D
    maintenance
    Privacy-first Telegram MCP server enabling maintainers to triage chats, inspect context, search messages, draft replies, and send authorized messages locally without a cloud relay.
    32 npm
    1
    MIT

  • codex-telegram

    briejhxh
    A
    license
    A
    quality
    C
    maintenance
    Enables local, privacy-first control of a personal Telegram account through MCP, using TDLib to read chats, send and reply to messages, search, transfer files, and interact with approved inline buttons.
    20
    MIT

  • Fast MCP Telegram

    leshchenko1979
    A
    license
    A
    quality
    A
    maintenance
    Fast MCP Telegram — Production-grade Telegram MCP server with direct MTProto API, multi-user ACL, dual transport (stdio + HTTP SSE), voice transcription, and context-optimized design. One-command setup with uvx fast-mcp-telegram
    8
    49
    MIT

  • telegram-notes-mcp

    RaspizDIYs
    A
    license
    A
    quality
    C
    maintenance
    A local MCP server that enables full-text and semantic search over your own Telegram chats using your personal MTProto login, with everything running locally.
    7
    MIT
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

C2.5/5.0

Scored across 61 tools

Disambiguation2/5

Several clusters overlap heavily: send/upload/photo/voice/album all send media, search/searchall/searchin all search the mirror, and export/export_contacts, import/import_contacts, ban/kick/block, schedule/scheduled/cancel, draft/drafts, pin/pinned, and react/reactions blur boundaries. Descriptions help somewhat, but an agent could easily misselect among these near-duplicates.

Naming Consistency2/5

Mostly lowercase, but patterns are inconsistent: some compounds use underscores (add_contact, delete_contact, block_list, del_photo), others concatenate (setname, searchall, searchin, setbio, setphoto), and some are noun_verb (folder_new, folder_rm) while others are verb_noun (add_contact). The abbreviation mix of 'del_photo' versus 'delete_contact' further breaks consistency.

Tool Count1/5

61 tools is excessive for a chat client MCP. Many are micro-operations (typing, status, notify, wait, watch) or near-duplicate media/search/contact commands, inflating the surface far beyond a well-scoped set.

Completeness4/5

The surface is broad—auth, messaging, media, contacts, groups/channels, folders, profiles, sync/search, scheduling, drafts, and session export/import/wipe. Gaps include creating/joining/leaving chats, inviting members, archiving/muting, and detailed chat info, but these are minor for most workflows.

Maintenance

ActivityNo data
ResponsivenessNo issues

Resources