{"_id":"@bossforce.ai/mcp-telegram-bot","name":"@bossforce.ai/mcp-telegram-bot","dist-tags":{"latest":"0.2.0"},"versions":{"0.2.0":{"name":"@bossforce.ai/mcp-telegram-bot","version":"0.2.0","type":"module","repository":{"type":"git","url":"git+https://github.com/bossforce-ai/bossforce-tools.git","directory":"mcps/messaging/telegram-bot"},"publishConfig":{"access":"public"},"bin":{"bossforce-mcp-telegram-bot":"dist/bin.js"},"dependencies":{"zod":"^4.4.3","@bossforce.ai/mcp-core":"0.3.0"},"devDependencies":{"@bossforce.ai/mcp-testkit":"0.0.0"},"scripts":{"build":"tsc -p tsconfig.json","test":"node --test \"dist/*.test.js\""},"_id":"@bossforce.ai/mcp-telegram-bot@0.2.0","description":"MCP server for the Telegram **Bot API** (a bot identity created via @BotFather). For acting as a personal Telegram account (MTProto), see a future `telegram-user` server — that is a different API with different auth and risks.","bugs":{"url":"https://github.com/bossforce-ai/bossforce-tools/issues"},"homepage":"https://github.com/bossforce-ai/bossforce-tools#readme","_integrity":"sha512-XRUgp2rXDDUZgCxlau0IrAK14IVzJ8bbB2RSybj525rYXVKcO1H12ojGY6OUshuUCZSKKfhne+GJ3FiJkdqg7w==","_resolved":"C:\\Users\\user\\AppData\\Local\\Temp\\a458c13bd03a7489d2ec41231dc772e5\\bossforce.ai-mcp-telegram-bot-0.2.0.tgz","_from":"file:bossforce.ai-mcp-telegram-bot-0.2.0.tgz","_nodeVersion":"22.18.0","_npmVersion":"10.9.3","dist":{"integrity":"sha512-XRUgp2rXDDUZgCxlau0IrAK14IVzJ8bbB2RSybj525rYXVKcO1H12ojGY6OUshuUCZSKKfhne+GJ3FiJkdqg7w==","shasum":"16b82cab8afae5d6e54dda576d9e4e041796cc16","tarball":"https://registry.npmjs.org/@bossforce.ai/mcp-telegram-bot/-/mcp-telegram-bot-0.2.0.tgz","fileCount":26,"unpackedSize":22576,"signatures":[{"keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U","sig":"MEUCIQDyu9Q9K7QYcozy5bYpnca75UbXeD+TGH5ujx1XuKhlggIgadPi6U27BPL3OWIhz4+Fz45mxFiHg+1f5T1O/FxRXao="}]},"_npmUser":{"name":"bossforce.ai","email":"bossforce.ai@gmail.com"},"directories":{},"maintainers":[{"name":"bossforce.ai","email":"bossforce.ai@gmail.com"}],"_npmOperationalInternal":{"host":"s3://npm-registry-packages-npm-production","tmp":"tmp/mcp-telegram-bot_0.2.0_1780985505281_0.573632180670075"},"_hasShrinkwrap":false}},"time":{"created":"2026-06-09T06:11:45.018Z","0.2.0":"2026-06-09T06:11:45.412Z","modified":"2026-06-09T06:11:45.737Z"},"maintainers":[{"name":"bossforce.ai","email":"bossforce.ai@gmail.com"}],"description":"MCP server for the Telegram **Bot API** (a bot identity created via @BotFather). For acting as a personal Telegram account (MTProto), see a future `telegram-user` server — that is a different API with different auth and risks.","homepage":"https://github.com/bossforce-ai/bossforce-tools#readme","repository":{"type":"git","url":"git+https://github.com/bossforce-ai/bossforce-tools.git","directory":"mcps/messaging/telegram-bot"},"bugs":{"url":"https://github.com/bossforce-ai/bossforce-tools/issues"},"readme":"# @bossforce.ai/mcp-telegram-bot\n\nMCP server for the Telegram **Bot API** (a bot identity created via @BotFather).\nFor acting as a personal Telegram account (MTProto), see a future\n`telegram-user` server — that is a different API with different auth and risks.\n\n## Credentials\n\n| Env                  | How to obtain                                                          |\n| -------------------- | ---------------------------------------------------------------------- |\n| `TELEGRAM_BOT_TOKEN` | Create a bot via [@BotFather](https://t.me/BotFather), copy the token. |\n\nThe token is read lazily, so the server boots and answers `tools/list` without\nit; calls fail with an `auth` error until it is set.\n\n## Tools\n\n| Tool           | Arguments                                                                         | Returns                             |\n| -------------- | --------------------------------------------------------------------------------- | ----------------------------------- |\n| `get_me`       | —                                                                                 | Bot `User`                          |\n| `send_message` | `chat_id`, `text`, `parse_mode?`, `reply_to_message_id?`, `disable_notification?` | sent `Message`                      |\n| `send_photo`   | `chat_id`, `photo` (URL or file_id), `caption?`, `parse_mode?`                    | sent `Message`                      |\n| `get_updates`  | `offset?`, `limit?`, `timeout?`                                                   | `{ updates: Update[] }`             |\n| `get_file`     | `file_id`                                                                         | image content (photos) or file blob |\n\nResults are Telegram's native objects, returned as `structuredContent`.\n\n### Polling\n\n`get_updates` is polling-based: pass `offset = last update_id + 1` to acknowledge\nprocessed updates. Real-time delivery needs a separate poller or webhook, which\nis out of scope for this server.\n\n## Develop\n\n```bash\npnpm --filter @bossforce.ai/mcp-telegram-bot build\npnpm --filter @bossforce.ai/mcp-telegram-bot test\n```\n\nRegenerate the tools/list snapshot after an intentional signature change:\n\n```bash\nUPDATE_SNAPSHOTS=1 pnpm --filter @bossforce.ai/mcp-telegram-bot test\n```\n","readmeFilename":"README.md","_rev":"1-5df7486684cd9488c5a064a81e328b36"}