Medium commands it can verify
Gemini CLI runs postqueen and reads the JSON back, so it can confirm which Medium stories exist and at what times instead of reporting success it did not check.
Queue Medium stories 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 Medium stories 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 Medium stories exist and at what times instead of reporting success it did not check.
Tell Gemini CLI when your readers are most active and it schedules stories into that window on Medium, day after day, without reminders.
Gemini CLI hands postqueen the full draft, formatting included, and it lands on your Medium publications as complete stories, ready for readers.
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 readers on Medium until you do.
Gemini CLI calls postqueen to list your connected publications and sees what Medium supports, so drafts start from real capabilities, not guesses.
Give it the brief. The agent writes Medium-shaped stories and proposes publish times that match when your readers 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 Medium tools are there in every session. It also runs commands, so the CLI covers the same Medium stories 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 stories it creates, so your readers see them at the right moment.
Only if you ask it to. Tell it to save drafts and nothing is scheduled: the stories 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 Medium stories 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 postqueen cloud plan comes with a 7-day free trial with unlimited posts, and you can cancel anytime. The open source version is also free to self-host if you want to run everything on your own infrastructure.
An integration token, which you create in your Medium account settings. postqueen uses it to publish through the official API under your profile at the exact time you schedule. No password sharing and no browser automation involved.
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.