Skip to main content
Glama
alexmakeev

telegram-user-mcp

by alexmakeev

telegram-user-mcp

Telegram user-account integration for MCP (Model Context Protocol), built on Telethon. Exposes Telegram operations (read/send messages, manage chats, etc.) to an MCP client over stdio or sse.

This is a containerized fork of chigwell/telegram-mcp.

Image

A public image is built by CI on every push to main and published to GHCR:

ghcr.io/alexmakeev/telegram-user-mcp:latest

Related MCP server: telegram-mcp

Configuration (runtime only)

All credentials are provided at runtime as environment variables — nothing is baked into the image. Obtain TELEGRAM_API_ID / TELEGRAM_API_HASH from https://my.telegram.org (API development tools).

Variable

Required

Description

TELEGRAM_API_ID

yes

Telegram API id

TELEGRAM_API_HASH

yes

Telegram API hash

TELEGRAM_SESSION_NAME

no

File-session name (default telegram_user)

TELEGRAM_SESSION_DIR

no

Directory for the file session (default /app/sessions)

TELEGRAM_SESSION_STRING

no

Portable string session (alternative to a file session)

TRANSPORT

no

stdio (default) or sse

LOG_LEVEL

no

Log level (default INFO)

Authenticating

You need either a session string or a session file for an authorized account:

  • String session: python session_string_generator.py (interactive), then set TELEGRAM_SESSION_STRING.

  • File session (QR login): python qr_auth.py, then mount the resulting sessions/ directory into the container.

A Telegram session grants full access to the account. Never commit session files or session strings. They are git-ignored here by default.

Run

docker run --rm \
  -e TELEGRAM_API_ID=... \
  -e TELEGRAM_API_HASH=... \
  -e TELEGRAM_SESSION_STRING=... \
  ghcr.io/alexmakeev/telegram-user-mcp:latest

License

Apache-2.0 (inherited from the upstream project). See pyproject.toml for authorship.

A
license - permissive license
Not graded
quality - not tested
B
maintenance

Maintenance

Maintainers
Response time
Release cycle
Releases (12mo)
Commit activity

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Servers

  • A
    license
    Not graded
    quality
    A
    maintenance
    Drives a personal Telegram account from the terminal or via MCP, enabling AI assistants to list chats, send/edit messages, fetch history, manage groups, and more with tiered read/write/destructive permissions.
    1
    MIT
  • A
    license
    Not graded
    quality
    C
    maintenance
    Enables MCP-compatible clients like Claude and Cursor to interact with Telegram accounts, supporting messaging, chat management, contacts, media, and admin operations via Telethon.
    Apache 2.0
  • A
    license
    A
    quality
    B
    maintenance
    Enables use of a personal Telegram account within MCP clients for reading and sending messages, searching chats, and managing media, all running locally.
    16
    27
    MIT
  • A
    license
    Not graded
    quality
    A
    maintenance
    Exposes a Telegram user account via MCP, enabling AI agents to send, read, and manage messages, chats, and media using full MTProto access through Telethon. It wraps Telethon behind a JSON HTTP API and MCP endpoint, allowing agents to interact with Telegram as the authenticated user.
    1
    Do What The F*ck You Want To Public

View all related MCP servers

Related MCP Connectors

  • Telegram bridge for your MCP-compatible agent. Bidirectional, no LLM in our stack.

  • Multi-tenant Telegram gateway for AI agents — HTTP+stdio, 8 tools, MTProto User API

  • MCP connector for iMessage & Contacts via a local Mac agent + Vercel relay

View all MCP Connectors

Latest Blog Posts

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/alexmakeev/telegram-user-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server