Telegram commands it can verify
Gemini CLI runs postqueen and reads the JSON back, so it can confirm which Telegram messages exist and at what times instead of reporting success it did not check.
Queue Telegram messages from the terminal. Gemini CLI runs every postqueen command and reads the JSON back, so it can check what it scheduled.
Run the postqueen CLI directly, or add the MCP endpoint to your Gemini CLI settings and ask for Telegram messages in plain language.
MCP supportednpm install -g postqueenexport POSTQUEEN_API_KEY=your_api_key # Or MCP, in your Gemini CLI settings:# { "mcpServers": { "postqueen": {# "url": "https://api.postqueen.ai/mcp/KEY"# } } }Gemini CLI runs postqueen and reads the JSON back, so it can confirm which Telegram messages exist and at what times instead of reporting success it did not check.
Tell Gemini CLI when your channels and groups are busiest and it schedules messages into that window on Telegram, day after day, without reminders.
Gemini CLI lists your connected channels and groups before it posts, so messages land exactly where they should and announcements stay consistent.
Ask Gemini CLI for drafts only. They sit on the postqueen calendar unscheduled, so you can edit them and pick the time yourself, and nothing reaches your subscribers on Telegram until you do.
Gemini CLI calls postqueen to list your connected channels and groups and sees what Telegram supports, so drafts start from real capabilities, not guesses.
Give it the brief. The agent writes Telegram-shaped messages and proposes publish times that match when your subscribers are around.
Look over the queue on the postqueen calendar and change anything you want. postqueen publishes each post at its time, and Gemini CLI can pull the results after.
Gemini CLI reads these limits from postqueen before it composes, so a draft that would be rejected never reaches the queue.
Scheduling, AI drafts, analytics and team roles, in one guide.
Over MCP, registered once in Gemini CLI's own config so the Telegram tools are there in every session. It also runs commands, so the CLI covers the same Telegram messages when you would rather script them; both use the same API key.
Yes. Give it exact slots or a rule like mornings at nine and it sets publish times on the messages it creates, keeping your channels and groups active on a steady rhythm.
Only if you ask it to. Tell it to save drafts and nothing is scheduled: the messages wait on the calendar until you set a time. Tell it to schedule, and they go out at the times you can see, which is the setup most people move to once they trust the output.
Yes. postqueen connects 30 channels, so Gemini CLI can turn the same brief into Telegram messages plus adapted versions for every other channel you run.
No. The agent uses your regular API key and plan limits: unlimited posts on every plan, and channel counts from 5 on Creator up to uncapped on Ultimate.
Yes. Every cloud plan starts with a 7-day free trial and unlimited posts. Self-hosting the open source version is free.
Through a bot using the official Telegram Bot API. You add the bot to your channel or group, promote it to admin with the Post Messages right, and scheduled posts publish automatically. Setup takes a couple of minutes per channel.
Queue this week's posts in minutes, or hand the whole thing to your favorite AI. postqueen keeps publishing either way.
Seven days free. Cancel in one click from settings.