@fre4x/telegram 1.1.8 → 1.1.9

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (3) hide show
  1. package/README.md +2 -1
  2. package/dist/index.js +6661 -6647
  3. package/package.json +2 -3
package/README.md CHANGED
@@ -18,12 +18,13 @@ npm run build
18
18
 
19
19
  ## Configuration
20
20
 
21
- This MCP server requires environment variables to secure its endpoints and access the Telegram API. You can either provide these via a local `.env` file (for development) or directly inside your Claude Desktop / MCP client JSON configuration (recommended for production).
21
+ This MCP server requires environment variables to secure its endpoints and access the Telegram API. Provide them in your Claude Desktop / MCP client JSON configuration. For local development, export the same variables in your shell (or `set -a; source .env; set +a`). The server does not load `.env` files itself.
22
22
 
23
23
  ### Environment Variables
24
24
 
25
25
  - `TELEGRAM_BOT_TOKEN` **(Required)**: Your bot's API token. Obtain this by talking to [@BotFather](https://t.me/botfather).
26
26
  - `ALLOWED_USER_ID` **(Required)**: The primary Telegram numeric user ID allowed to send messages to the bot in private chats and use commands. Obtain this via [@userinfobot](https://t.me/userinfobot).
27
+ - `TELEGRAM_STATE_PATH` *(Optional)*: Override the persisted chat-state file path. Leading `~` / `~/` is expanded by the server (not the shell).
27
28
  - `ENABLE_RECIPIENT_WHITELIST` *(Optional)*: Set to `"true"` to enforce a strict whitelist of users/groups the bot is allowed to message.
28
29
  - `ALLOWED_RECIPIENTS` *(Optional)*: A comma-separated list of Telegram numeric IDs (e.g., `1234567,-100987654`) that Claude is permitted to message.
29
30