Reported issues for Telegram (mcp-telegram)

Pod holds 16 of 31 problems reported by people outside the maintainer team. Issues filed by the project's own owners, members and collaborators are excluded entirely — a maintainer's release checklist is not a warning to a prospective user.

Back to Telegram (mcp-telegram).

Most discussed

Telegram feature parity — cover 90% of what a regular user can do

Goal

Cover ~90% of what a regular Telegram user can do.

Status: v1.23.0 shipped with 22 tools (was 11). Most P0/P1 implemented via PR #35.

Current Tools (22)

Auth (5) · Messages (5) · Chats (8) · Media (3) · Contacts (2) · Reactions (1) · Extras (4) Plus 11 new: edit, delete, forward, mark_as_read, get_dialogs, get_chat_info, send_reaction, create_poll, manage_invite_links, send_file, add_contact

Progress

P0: Must-Have ✅

#18 — edit_message (v1.23.0)
#19 — mark_as

Read the thread · 2026-04-05 · closed · 3 comments

Remote deployments: file paths resolve on the daemon host, so downloads never reach the client

Problem

When the MCP server runs on a remote host (the common setup for a userbot: a VPS holds the session, the MCP client runs on a laptop, stdio is bridged over SSH), every file-shaped tool operates on the wrong filesystem.

telegram-download-media writes the media to the VPS and replies Media downloaded to /path — a path that does not exist on the machine that asked for it.
telegram-send-file, telegram-send-voice, telegram-send-video-note, telegram-send-story, `telegra

Read the thread · 2026-08-06 · open · outside contributor · 2 comments

Master daemon never recovers from a dropped MTProto connection — all tool calls fail with 'IPC call timeout' until killed

Summary

Once the master daemon loses its MTProto connection, it never recovers. It stays alive, keeps accepting IPC clients and keeps serving tool calls that can never complete, so every call from every client fails with IPC call timeout: <tool> until the master is killed by hand.

I hit this after the daemon had been up for ~22 hours. The process was healthy and listening on daemon.sock, but had zero TCP connections to Telegram:

$ cat ~/.mcp-telegram/daemon.lock
1836
$ ps -o pi

[Read the thread](https://github.com/mcp-telegram/mcp-telegram/issues/71) · 2026-07-27 · closed · external user · 2 comments

### report_spam — report spam messages or users

## Description
Add `report_spam` tool to report spam in chats.

## Parameters
- `chatId` (required) — chat identifier
- `messageIds` (optional) — specific message IDs to report
- `reason` (optional) — spam, violence, pornography, child_abuse, copyright, other

## Telegram API
`messages.report`, `account.reportPeer`

[Read the thread](https://github.com/mcp-telegram/mcp-telegram/issues/33) · 2026-04-05 · closed · 2 comments

### get_forum_topics — list and manage forum topics

## Description
Enhance forum support with dedicated topic management tools.

Currently forum topics are partially supported in `get_messages`. Add dedicated tools:

## Tools
### `get_forum_topics`
- `chatId` (required) — forum group identifier
- `limit` (optional) — max topics to return

### `create_forum_topic`
- `chatId` (required) — forum group identifier
- `title` (required) — topic title
- `iconColor` (optional) — topic icon color
- `iconEmojiId` (optional) — custom emoji ID for icon

### `

[Read the thread](https://github.com/mcp-telegram/mcp-telegram/issues/27) · 2026-04-05 · closed · 2 comments

### block_user / unblock_user — block and unblock users

## Description
Add tools to block and unblock users.

## Tools
### `block_user`
- `userId` (required) — user identifier or username

### `unblock_user`
- `userId` (required) — user identifier or username

## Telegram API
`contacts.block` / `contacts.unblock`

[Read the thread](https://github.com/mcp-telegram/mcp-telegram/issues/25) · 2026-04-05 · closed · 2 comments

### edit_chat_settings — update group/channel title, description, permissions

## Description
Add `edit_chat_settings` tool to modify group/channel settings.

## Parameters
- `chatId` (required) — chat identifier
- `title` (optional) — new chat title
- `description` (optional) — new description/about
- `permissions` (optional) — member permissions object (send messages, media, polls, etc.)
- `slowMode` (optional) — slow mode delay in seconds (0 to disable)

## Telegram API
`channels.editTitle`, `channels.editAbout`, `channels.editBanned` for permissions

[Read the thread](https://github.com/mcp-telegram/mcp-telegram/issues/24) · 2026-04-05 · closed · 2 comments

### [Feature Request / Question] Support sending paid media (sendPaidMedia) via Telegram MCP

### Description

Does the project currently support sending paid media content (e.g., photos or videos unlocked via Telegram Stars) to Telegram users?

If it is already supported, could you please provide guidance or examples on how to configure or call the corresponding Tool / API?

If not, are there any plans to add support for the `sendPaidMedia` method in upcoming releases?

### Use Case

When interacting with Telegram via the MCP service, we would like to directly send media resources (phot

[Read the thread](https://github.com/mcp-telegram/mcp-telegram/issues/70) · 2026-07-23 · open · external user · 1 comment

## Most recent

### Windows + Node: server crashes at startup — IPC listens on a filesystem path (listen EACCES); needs \\.\pipe\ mapping on win32

## Summary

Since the master/client IPC architecture, the npm package cannot start on Windows with Node.js. `startOwner()` (dist/master.js) listens on `join(sessionDir, "daemon.sock")` — a filesystem path. On Windows, Node's `net.Server.listen(path)` only supports the named-pipe namespace (`\\.\pipe\` / `\\?\pipe\`, see [Node docs, "IPC support"](https://nodejs.org/api/net.html#identifying-paths-for-ipc-connections)), so the first launch (which becomes master) dies immediately:

[mcp-telegra

Read the thread · 2026-07-15 · closed · external user · 1 comment

fix: address Copilot review feedback from PR #35

PR #35 was merged with 29 unresolved Copilot review comments. This issue tracks all the feedback as a cleanup checklist.

🛡️ Input Validation & Safety

`mute-chat`

duration=0 is treated as "not provided" due to falsy check — use explicit undefined check instead
Negative duration values are not validated — add nonnegative() guard
Large duration values can overflow 32-bit int — clamp or reject
Magic number 2147483647 should be extracted to a named constant (e

Read the thread · 2026-04-05 · closed · 1 comment

update_profile — update own name, bio, username

Description

Add update_profile tool to update the user's own profile information.

Parameters

firstName (optional) — new first name
lastName (optional) — new last name
bio (optional) — new bio/about text (max 70 chars, 300 for Premium)
username (optional) — new username

Telegram API

account.updateProfile, account.updateUsername

Read the thread · 2026-04-05 · closed · 1 comment

set_privacy — configure privacy settings

Description

Add set_privacy tool to configure account privacy settings.

Parameters

setting (required) — one of: phone_number, last_seen, profile_photo, forwards, calls, groups, bio
rule (required) — one of: everyone, contacts, nobody
allowUsers (optional) — array of user IDs to add as exceptions (always allow)
disallowUsers (optional) — array of user IDs to add as exceptions (never allow)

Telegram API

account.setPrivacy with various InputPrivacyKey* types

Read the thread · 2026-04-05 · closed · 1 comment

manage_sessions — view and terminate active sessions

Description

Add tools to view and manage active Telegram sessions (logged-in devices).

Tools

`get_active_sessions`

Returns list of all active sessions with device info, IP, location, last active time.

`terminate_session`

sessionId (required) — hash of the session to terminate
terminateAll (optional) — terminate all other sessions except current

Telegram API

account.getAuthorizations, account.resetAuthorization

Read the thread · 2026-04-05 · closed · 1 comment

set_auto_delete — configure auto-delete timer for chats

Description

Add set_auto_delete tool to configure message auto-deletion in chats.

Parameters

chatId (required) — chat identifier
period (required) — auto-delete period in seconds. Common values: 86400 (1 day), 604800 (1 week), 2592000 (1 month). Use 0 to disable.

Telegram API

messages.setHistoryTTL

Read the thread · 2026-04-05 · closed · 1 comment

manage_chat_folders — get, create, edit, delete chat folders

Description

Add tools to manage Telegram chat folders (filters).

Tools

`get_chat_folders`

Returns list of user's chat folders with their filters.

`manage_chat_folder`

action — "create", "edit", "delete"
title (optional) — folder name
includedChats (optional) — chat IDs to include
excludedChats (optional) — chat IDs to exclude
includeTypes (optional) — auto-include types: contacts, non_contacts, groups, channels, bots

Telegram API

`messages.getDialogFilters

Read the thread · 2026-04-05 · closed · 1 comment

manage_invite_links — create, get, and revoke invite links

Description

Add tools to manage chat invite links.

Tools

`get_invite_link`

chatId (required) — chat identifier

`create_invite_link`

chatId (required) — chat identifier
expireDate (optional) — link expiration timestamp
memberLimit (optional) — max number of joins
requestApproval (optional) — require admin approval

`revoke_invite_link`

chatId (required) — chat identifier
link (required) — the invite link to revoke

Telegram API

`messages.exportCh

Read the thread · 2026-04-05 · closed · 0 comments

The remaining reports are on the project's issue tracker.