MCP Tools DirectoryAbout this integration
Provision owner-confirmed isolated Telegram Managed Bot instances.
- Transport
- stdio
- Authentication
- unknown
- Initial setup
- user-authorization
- Runtime
- unattended
- Evidence
- documented
- Version
- 0.1.0
- Package
- telegram-managed-bot-factory
- Last compatibility test
- Not independently tested
Connect your agent
telegram-managed-bot-factoryPublisher documentation reviewed only. Installation, systemd, Hermes, Telegram, credential isolation, and external side effects were not exercised. The publisher explicitly does not claim exactly-once external effects.
Capabilities: managed bot creation requests, bot status, profile attachment, bot pause and resume, bounded export and purge flows
Connected profiles
Additional details
io.github.laser54/bot-factory
Source ↗ · Checked 2026-09-170.1.0
Source ↗ · Checked 2026-09-17CC0-1.0; package licenses are separate
Source ↗ · Checked 2026-09-17pypi
Source ↗ · Checked 2026-09-17telegram-managed-bot-factory
Source ↗ · Checked 2026-09-190.2.3
Source ↗ · Checked 2026-09-19After an interactive terminal-only installation, a persistent systemd user worker and a nine-tool Python stdio server operate locally; every child creation still requires confirmation in Telegram.
Source ↗ · Checked 2026-09-19Authentication does not fit the native key taxonomy: the manager-bot credential is collected through hidden terminal input outside MCP, the owner is enrolled during setup, and creation approval occurs in Telegram. The credential must not be placed in environment variables or MCP arguments.
Source ↗ · Checked 2026-09-19The installer registers the nine-tool stdio server with Hermes after verifying the persistent worker; the manifest exposes bot-factory-mcp as the MCP entry point.
Source ↗ · Checked 2026-09-19Publisher documentation reviewed; package and integration endpoint not executed or independently security-audited.
Source ↗ · Checked 2026-09-19