Docker Telethon Plus

devops-infra MCP Server

Your Telegram account, but it takes HTTP requests. Wraps Telethon — the real MTProto userbot client, not that neutered Bot API garbage — behind a JSON HTTP API and a Model Context Protocol endpoint.

Verified
devops-infradevops-infradocker
4 views0 stars0 forksWTFPL

Why This Matters

Discovered via github-topic:mcp and last synced 3mo ago.

Verified
Source
github-topic:mcp
Stars
0
Last synced
3mo ago
Install
Check source

Install

Install instructions not detected yet

Check the source repository for the latest setup steps.

View source instructions
45
Tools
0
Resources
0
Prompts
Standard I/O
Transport

Available Tools (45)

Telethon

<----> Servers

TELETHON_DEVICE_MODEL

no

archived

bool

TELETHON_API_ID

yes

TELETHON_API_HASH

yes

TELETHON_SESSION

yes

TELETHON_FLOOD_SLEEP_THRESHOLD

no

chat

string

limit

int

text

string

megagroup

bool

TELETHON_HTTP_LISTEN_ADDRESS

no

Format

Example

search

string

from_chat

string

file_url

string

TELETHON_LOG_LEVEL

no

Username

`@psyb0t`

Field

Type

to_chat

string

caption

string

Variable

Required

TELETHON_SYSTEM_VERSION

no

reply_to

int

max_bytes

int

400

Bad JSON, validation failure, or Telethon said the input is nonsense. Body has details.

TELETHON_REQUEST_TIMEOUT

no

me

### Quick reference

Param

Type

parse_mode

string

TELETHON_APP_VERSION

no

silent

bool

message_ids

list[int]

max_id

int

401

Missing or wrong Bearer token (only when `TELETHON_AUTH_KEY` is set).

TELETHON_DOWNLOAD_DIR

no

title

string

link_preview

bool

revoke

bool

404

Unknown endpoint.

TELETHON_AUTH_KEY

no

offset_id

int

502

Telegram threw an RPC error (`FloodWaitError`, `ChatWriteForbiddenError`, etc.). Body has the error class and message.

force_document

bool

Status

When