Gemini CLI is the free-and-fast way into terminal agents, and it speaks MCP, so it plugs into planpo.st the same way Claude Code does: one settings entry, then the agent can draft, schedule and report.
The pairing suits scripted and repeatable work. Weekly planning runs, bulk rewrites, the kind of jobs where you want an agent doing the same reliable thing every Monday.
Gemini CLI is Google's open-source terminal agent for the Gemini models. MCP servers go in settings.json globally or per project. One sharp edge: remote servers use the httpUrl key, not url, and the wrong key fails silently, which is why our setup page spells it out.
Read content-plan.md, draft this week's posts for LinkedIn and Threads, and schedule them at the best times.
The agent reads your plan file, drafts per network, calls get_best_times, and fills the week with create_post. Run it every Monday and the calendar stops being a chore.
Here are 20 post ideas in ideas.csv. Create them all as drafts spread over the next month.
bulk_create_posts takes the whole set in one call. Twenty drafts appear, dated and platform-tagged, ready for a review pass in the dashboard.
Which platform earned the most per post last month?
The agent pulls get_revenue_overview, divides attributed revenue by post count per platform, and gives you a ranking backed by payment data. That number quietly decides where next month's effort goes.
Plenty of tools let an agent post. The difference here is what comes back: every link in a scheduled post can be tracked, payments from Stripe, Shopify or RevenueCat are matched to the exact post that caused them, and your agent can read those numbers with the same connection it used to publish. Gemini CLI does not just post for you, it finds out whether the post worked.
Google's terminal agent. Uses httpUrl for remote servers. Grab an API key from Settings, add the server, hosted or local, and the tools appear. The full config, with the sharp edges called out, is on the setup page.
What Gemini CLI can reach