@dikacode/telegram-mcp 1.0.3

Fixed

• telegram-mcp update did nothing when run as a command: exit 0, no output. The module entrypoint worked, the documented form did not.
• telegram-mcp update --help now describes update instead of printing the server usage.
• A unit check runs the real binary and asserts the plan prints, so the silent path cannot come back.

@dikacode/telegram-mcp 1.0.2

@dikacode/telegram-mcp 1.0.2

CLI styling, interactive UI, and telegram-mcp update.

What's new in 1.0.2

• CLI UI & Styling:
  • Modern ASCII wordmark banner with clean framing.
  • SGR color palettes (dim, cyan, teal, green, warning yellow, error red) with automatic fallback for non-TTY, NO_COLOR, and TERM=dumb.
  • Animated spinner and ordered step headers during terminal login and setup.
  • Formatted status reports with icons for telegram-mcp doctor.
• Automatic Install-Aware Updater:
  • telegram-mcp update auto-detects installation method (global npm, npx run, or git clone) and performs the exact corresponding update.
  • telegram-mcp update --check (or --dry-run) reports current vs registry version without modifying files.
• Diagnostics & Stability:
  • Fixed fallback version behavior when package.json is unreadable.
  • 73 unit tests covering updater, version comparator, and argument isolation.

Install

npx -y @dikacode/telegram-mcp

Or globally:

npm install -g @dikacode/telegram-mcp
telegram-mcp

@dikacode/telegram-mcp 1.0.1

@dikacode/telegram-mcp 1.0.1

Update path made explicit. 1.0.0 could only be updated by knowing npm's
commands by heart: there was no way to ask the installed copy its version, and
no signal that a newer release existed.

A local MCP server that connects an AI CLI agent to a personal Telegram account
over MTProto. It runs on your machine, speaks JSON-RPC over stdio, and keeps the
session on disk. No bot token, no hosted relay.

Install

npx -y @dikacode/telegram-mcp

Or globally:

npm install -g @dikacode/telegram-mcp
telegram-mcp

MCP client config:

{
  "mcpServers": {
    "telegram": {
      "command": "npx",
      "args": ["-y", "@dikacode/telegram-mcp"]
    }
  }
}

You need Node.js 20 or newer and an api_id / api_hash from
https://my.telegram.org/apps. Client-specific snippets are in the
README.

The tarball attached below is the same artifact that was published to npm.

Updating from 1.0.0

npm install -g @dikacode/telegram-mcp@latest     # global install
npx -y @dikacode/telegram-mcp@latest             # one-off

An unpinned npx config needs nothing: npm resolves latest on every start.

What's new in 1.0.1

• telegram-mcp --version / -v prints the version and exits before the
  stdio transport starts. --help / -h prints usage, setup steps and the
  upgrade commands. Any other argument still falls through to serving, so a
  client passing its own flags cannot break the server.
• Update notice. After the transport is live, the server asks the registry
  for dist-tags.latest and prints one line to stderr when something newer
  exists, naming the upgrade command for the install type in use. 800 ms
  timeout, cached 24 hours, never blocks startup, never writes to stdout.
• TELEGRAM_UPDATE_CHECK=0 turns the lookup off, and
  TELEGRAM_UPDATE_CHECK_TIMEOUT_MS caps the wait.
• telegram_doctor reports the installed version and the newest release it
  knows about from the cache. Informational only — an available update never
  flips healthy to false.
• The version is now read from package.json at runtime, so serverInfo,
  --version and the published tarball cannot drift apart.

What's included

• 69 tools for chats, messages, media, contacts, groups, channels,
  administration, sessions and the audit log.
• Login from chat, including two-step verification. Codes and 2FA passwords
  are held in memory for one call and never persisted.
• Strict input schemas and read-back verification for state-changing
  tools, so a successful request is not mistaken for a successful change.
• Cursor-based paging for history, in-chat search and global search.
• Optional allowlist and an audit log with secret arguments redacted.
• Cross-platform launcher for Linux, macOS and Windows.
• End-to-end harness that drives the built server over stdio, plus 72
  offline checks.

Verification

• CI runs typecheck, build and the offline checks on Ubuntu, macOS and Windows,
  against Node.js 20 and 22.
• The release tarball was installed into a clean prefix: telegram-mcp --version printed 1.0.1, and tools/list returned all 69 tools.
• The published tarball contains 34 files: the launcher, compiled dist/,
  README.md, LICENSE and package.json — no harness, no assets, no .env.

Known limitations

• This is a user-account client, not the Bot API. Telegram's terms apply, and
  automated behaviour can get an account limited or banned.
• Secret chats and voice/video calls are not exposed.
• Some operations need administrator rights; reactions in Saved Messages need
  Telegram Premium.
• telegram_clear_history removes at most 10,000 messages per call.

See CHANGELOG.md
for the full notes.

@dikacode/telegram-mcp 1.0.0

@dikacode/telegram-mcp 1.0.0

First public release. A local MCP server that connects an AI CLI agent to a
personal Telegram account over MTProto. It runs on your machine, speaks JSON-RPC
over stdio, and keeps the session on disk. No bot token, no hosted relay.

Install

npx -y @dikacode/telegram-mcp

Or globally:

npm install -g @dikacode/telegram-mcp
telegram-mcp

MCP client config:

{
  "mcpServers": {
    "telegram": {
      "command": "npx",
      "args": ["-y", "@dikacode/telegram-mcp"]
    }
  }
}

You need Node.js 20 or newer and an api_id / api_hash from
https://my.telegram.org/apps. Client-specific snippets are in the
README.

The tarball attached below is the same artifact that was published to npm.

What's included

• 69 tools for chats, messages, media, contacts, groups, channels,
  administration, sessions and the audit log.
• Login from chat, including two-step verification. Codes and 2FA passwords
  are held in memory for one call and never persisted.
• Strict input schemas and read-back verification for state-changing
  tools, so a successful request is not mistaken for a successful change.
• Cursor-based paging for history, in-chat search and global search.
• Optional allowlist and an audit log with secret arguments redacted.
• Cross-platform launcher for Linux, macOS and Windows.
• End-to-end harness that drives the built server over stdio, plus 64
  offline checks.

Verification

• CI runs typecheck, build and the 64 offline checks on Ubuntu, macOS and
  Windows, against Node.js 20 and 22.
• npx -y @dikacode/telegram-mcp was run from a clean npm cache and answered
  tools/list with all 69 tools.
• The release tarball was installed into a clean prefix and answered
  tools/list with all 69 tools.
• The published tarball contains 32 files: the launcher, compiled dist/,
  README.md, LICENSE and package.json.

Known limitations

• This is a user-account client, not the Bot API. Telegram's terms apply, and
  automated behaviour can get an account limited or banned.
• Secret chats and voice/video calls are not exposed.
• Some operations need administrator rights; reactions in Saved Messages need
  Telegram Premium.
• telegram_clear_history removes at most 10,000 messages per call.

See CHANGELOG.md
for the full notes.