An MCP server that connects to a personal Telegram account via MTProto (gram.js) so Claude can read, search, and reply to real Telegram DM conversations. It is intended for the `/ops:ops-inbox` use case and runs locally over stdio.
From the registry: Telegram personal-account MCP (MTProto user-auth). Read DMs, send messages, search across chats.
$ cd claude-ops/telegram-server && npm install$ TELEGRAM_API_ID=<your-telegram-api-id> TELEGRAM_API_HASH=<your-telegram-api-hash> TELEGRAM_PHONE=<your-phone-number> node index.js --authPlease install the `claude-ops-telegram-server` MCP server into my current AI client (that's you).
Required prerequisites (do these first if not already done):
- **Create Telegram API credentials** — Create a personal Telegram application at my.telegram.org/apps to obtain a Telegram API ID and API hash for user-auth access. (https://my.telegram.org/apps/)
- **Install server dependencies** — Install the Node.js dependencies in the telegram-server directory before running the server locally. Run: `cd claude-ops/telegram-server && npm install`
- **Generate Telegram session token** — Run the server once in interactive auth mode, enter the SMS code and 2FA password if prompted, and save the printed TELEGRAM_SESSION value securely. Run: `TELEGRAM_API_ID=<your-telegram-api-id> TELEGRAM_API_HASH=<your-telegram-api-hash> TELEGRAM_PHONE=<your-phone-number> node index.js --auth`
Canonical MCP server config (stdio transport):
- command: `node`
- args: ["/path/to/claude-ops/telegram-server/index.js"]
- required environment variables:
- `TELEGRAM_API_ID`: Telegram personal application API ID from my.telegram.org/apps. (example: `<your-telegram-api-id>`)
- `TELEGRAM_API_HASH`: Telegram personal application API hash from my.telegram.org/apps. (example: `<your-telegram-api-hash>`)
- `TELEGRAM_SESSION`: Telegram session string generated by the interactive first-run authentication step. (example: `<your-telegram-session>`)
- `TELEGRAM_PHONE`: Phone number for the authenticated Telegram account, in international format. (example: `<your-phone-number>`)
- optional environment variables:
- `TELEGRAM_ENABLED`: Optional flag mentioned for ops-unread detection enablement; not shown as required for the MCP server process itself. (example: `<true-or-false>`)
Note: This server authenticates as a personal Telegram user account via MTProto and runs locally over stdio. The README only documents local execution from the repo, not an npx/package-based install path.
Add this MCP server to my current client's config in the correct format for you. If you need secrets or credentials I haven't provided, ASK me — do not invent values or leave raw placeholders. After adding it, tell me how to verify the server is connected.TELEGRAM_API_IDrequiredTelegram personal app API ID used to authenticate with MTProtoTELEGRAM_API_HASHrequiredTelegram personal app API hash used to authenticate with MTProtoTELEGRAM_SESSIONrequiredSaved Telegram session token for authenticated accessTELEGRAM_PHONErequiredPhone number for the personal Telegram account used during authenticationReddit browser for AI assistants. Browse posts, search content, analyze users. No API keys needed.
Twitter X automation MCP - post schedule analytics engagement social media
MCP server for WhatsApp Cloud API (Meta) — messages, media, and templates via Graph API